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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment