Search Issue Tracker
Fixed
Votes
1
Found in
4.1.0f4
Issue ID
533268
Regression
No
Resources.LoadAll does not accept Path.DirectorySeparatorChar characters in the path.
Resources.LoadAll only accepts Path.AltDirectorySeparatorChar characters in the path. using Path.DirectorySeparatorChar fails.
if you try to construct a path using Path.Combine the Combine method uses Path.DirectorySeparatorChar to join paths.
Also a user could specify a path to a resource to load and they could type Path.DirectorySeparatorChar or Path.AltDirectorySeparatorChar.
This behavior is not in line with .net (and probably mono) behaviors.
Resources.LoadAll should treat Path.DirectorySeparatorChar & Path.AltDirectorySeparatorChar slashes the same.
Also the documentation does not mention this about using only Path.AltDirectorySeparatorChar characters.
NOTE: I did not test Resources.Load but I am assuming it behaves the same.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Unsupported texture format R16 for a swizzle" error and texture is not correctly rendered when using texture Swizzle and reimporting texture asset
- Tab order is incorrect after re-ordering
- [Ubuntu] Red squares instead of ticks in dropdown options
- Multiple simultaneous input with the touch screen sometimes leaves button in not default state
- Crash on ShowDelayedContextMenu(bool) when changing the Size options of a Visual Element in the UIToolkit Inspector
Add comment