Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
4.3.0b1
Issue ID
561529
Regression
No
Enum is named EditorSkin.Inspector and EditorSkin.Scene, and that it should be EditorSkin.Light and EditorSkin.Dark
EditorGUIUtility.GetBuiltinSkin(EditorSkin.Inspector)
The behavior in all previous versions of Unity (returning the currently active skin) was an error. The actual problem is that the enum is named EditorSkin.Inspector and EditorSkin.Scene, and that it should be EditorSkin.Light and EditorSkin.Dark, or something along those lines.
In short, although the behavior has *changed* in 4.3, it seems as though
the new behavior is in fact expected, but the enum needs to renamed at some point for better clarity.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
Add comment