Search Issue Tracker
Fixed in 6000.1.0b12
Fixed in 6000.0.7f1, 6000.1.X, 6000.2.X, future release
Votes
5
Found in
6000.0.0b12
6000.1.0a7
6000.2.0a1
Issue ID
UUM-67390
Regression
No
Property Attributes don't affect regular fields when "ApplyToCollection" is set to true
Steps to reproduce:
1. Open the “CollectionAttributesBug.zip” project
2. Open the "SampleScene"
3. Open the "ReadOnlyAttribute” script (Assets > Scripts)
4. Confirm that the “PropertyAttribute.applyToCollection” flag is set to true
5. In the Hierarchy window, select the “AttributeExample” GameObject
6. Observe the fields in the Inspector window
Expected results: regular fields are read-only
Actual results: regular fields lose the read-only attribute when applyToCollection is true
Reproducible with: 6000.0.b12
Couldn’t test with: 2021.3.36f1, 2022.3.21f1, 2023.2.13f1 ({{Assets\Scripts\ReadOnlyAttribute.cs(5,31): error CS1729: 'PropertyAttribute' does not contain a constructor that takes 1 argument}})
Reproducible on: Windows 10 (by reporter), Windows 11
Not reproducible on: No other environment tested
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
v0lt1369
Dec 08, 2024 03:01
The bug has only been fixed in Unity 6 for regular fields but nested fields still have this issue.