Search Issue Tracker
Fixed
Fixed in 2021.3.38f1, 2022.3.24f1, 2023.2.18f1, 6000.0.0b14
Votes
0
Found in
2021.3.36f1
2022.3.21f1
2023.2.14f1
6000.0.0b11
Issue ID
UUM-66687
Regression
No
Nested PropertyDrawer doesn't work when there's both an Attribute drawer and a Drawer for the type
How to reproduce:
1. Open the user’s attached “DrawerTests.zip” project
2. In the Project window, select “TestObject”
3. Observe the “CoolName” field in the Inspector window
Expected result: “CoolName” should appear as an int field
Actual result: “CoolName” uses the default inspector (a foldout and an int field named "value" inside)
Reproducible with: 2022.3.21f1, 2023.2.14f1, 2023.3.0b10
Could not test with: 2021.3.36f1 (“No GUI implemented” text appears near “CoolName” field)
Reproduced on: macOS 14.3.1 (Intel)
Not reproducible on: No other environment tested
Note: not reproducible without “[ChangeLabel("CoolName”)]” in TestObject.cs script
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 6000.0.0b14):
Fixed in: 6000.0.0b14