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
- UnityWebRequest returns "Curl error 5" instead of timing out when the Windows proxy auto-config script returns multiple proxies
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
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)