Search Issue Tracker
By Design
By Design in 2023.3.X
Votes
0
Found in
2021.3.30f1
2022.3.10f1
2023.1.14f1
2023.2.0b10
2023.3.0a5
Issue ID
UUM-49119
Regression
No
Custom field is Read-Only when used in Project Settings
How to reproduce:
1. Open the user's attached project
2. Open Edit>Project Settings...
3. Select "AuroraUI" in the Project Settings window
Expected results: “Test Int” is not greyed out
Actual results: “Test Int” is greyed out
Reproducible with: 2021.3.30f1, 2022.3.10f1, 2023.1.14f1, 2023.2.0b10, 2023.3.0a5
Reproducible on: Windows 10 22H2
Not reproducible on: No other environment tested
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note:
Serialized objects created with a ScriptableSingleton have the HideFlags.DontSave | HideFlags.HideInHierarchy; flags set. You can set your object as editable in the OnEnable method:
void OnEnable()
{
hideFlags &= ~HideFlags.NotEditable;
}
Resolution Note (2023.3.X):
Serialized objects created with a ScriptableSingleton have the HideFlags.DontSave | HideFlags.HideInHierarchy; flags set. You can set your object as editable in the OnEnable method:
void OnEnable()
{
hideFlags &= ~HideFlags.NotEditable;
}