Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.18f1
2022.2.6f1
2023.1.0b3
2023.2.0a1
Issue ID
UUM-26696
Regression
Yes
The value of a property in an element that is in an array cannot be changed when in Project Settings
Reproduction steps:
1. Open the “SettingsProvider-IMGUI-bug“ project
2. In Project Settings navigate to the “Bug/Sample” tab
3. Expand the “Multi Level Tester 2“ array
4. Expand “tester_2_1” and try to change any of its values (e.g. Name)
Expected result: the values can be changed
Actual result: the values cannot be changed
Reproduced in: 2020.2.0a13, 2021.3.18f1, 2022.2.6f1, 2023.1.0b3, 2023.2.0a1
Not reproduced in: 2020.2.0a12, 2020.3.45f1
Reproduced using: macOS 13.0.1 (Intel), Windows 11 (by reporter)
Note: fields work as expected in Inspector when selecting the “SampleSO” ScriptableObject
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
The fix for this issue is risky so we recommend either using [NonReorderable] attribute or using activateHandler and initialize asset editor as InspectorElement.
It is worth mentioning that the latter workaround will not require reworking asset Editor to UI Toolkit so the solution won't take up too much time.
Resolution Note (2023.2.X):
The fix for this issue is risky so we recommend either using [NonReorderable] attribute or using activateHandler and initialize asset editor as InspectorElement.
It is worth mentioning that the latter workaround will not require reworking asset Editor to UI Toolkit so the solution won't take up too much time.