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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment