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
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
Add comment