Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.2.0f3
Issue ID
980877
Regression
No
Custom Property Drawers are not allways called when calling Property Field
To reproduce:
1. Open the project, attached by the tester (propertyDrawerBug.zip).
2. Open the "scene" scene.
3. Select the "Test" game object in the hierarchy.
4. Observe how ValueTest class is drawn
Expected: if a serializable class A is drawn with a custom Property Drawer and it contains a serializable class B, which is has a custom Property Drawer defined for it, class B should be drawn with that custom Property Drawer, not the default one
Actual: a custom Property Drawer of a serializable class is ignored when an object of that class is a field of another class, which is drawn with a custom Property Drawer.
Reproduced in 5.6.4p3, 2017.1.2p2, 2017.2.0f3, 2017.2.1p1, 2017.3.0p3, 2018.1.0b4
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
- Polygons are created on the opposite side of the Sprite when the Sprite boundaries are above the edge of the Texture
- Render Graph Viewer Resource list becomes shrunk after using a filter that yields no results
- [Android] [Vulkan] "VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT" not added on some Android devices in "com.unity3d.player.UnityPlayerActivity/2D Colour Attachement"
- ResolveUsePasses now extracts passes from all subshaders including fallbacks, in contrast to documented behaviour
- [UIBuilder] Changes aren't detected on types implementing IList
Resolution Note:
with UIE out of experimental i suggest users to use it instead. Also, since it's only affecting a few users, it likely won't be fixed.