Search Issue Tracker
By Design
Votes
0
Found in
4.3.0f4
Issue ID
575954
Regression
No
DrawDefaultInspector() doesn't work properly
To reproduce:
1. Open a project
2. Open a scene with an object that has a sprite renderer
3. Click on the game object in the hierarchy view
4. Take a careful look at sprite renderer component in the Inspector
5. Delete "Editor" folder from the project view
6. Look at sprite renderer component again - now it looks different.
Editor folder includes only one script with DrawDefaultInspector()
Resolved as By Design since SpriteRenderer has a build-in custom Editor. DrawDefaultInspector shows the GUI the same as if there was no custom Editor. This looks different from the custom Editor GUI.
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Inconsistent ShaderGraph RGBA channels compared to the Inspector when "Alpha Is Transparency" is used
- Crash on "The GUID inside 'Assets/asset.png.meta' cannot be extracted by the YAML Parser." when opening the project
- Shadows disappear when looking at a certain angle in Scene view and using Cloud Shadows with Volumetric Clouds
- StackOverflowException freezes or silently crashes the Editor
- Microsoft Surface Device freezes when detaching and reattaching physical keyboard attachment to the device in Standalone Player for Windows
JeromeJ
Mar 10, 2018 16:42
DrawDefaultInspector DOESN'T show the custom editor. It shows the Debug mode one which doesn't contain the same info/utilities, some are missing (like the Order in layer)