Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2019.3
2019.3.10f1
2020.2
Issue ID
1243897
Regression
No
BindingExtensions.BindProperty binds a property to a field by its name
How to reproduce:
1. Open the project "BindProperty-bug"
2. Select the asset "Collection" in the Project window
3. Tick/untick the property "Is Enable" in the Inspector
Expected results: only the "Is Enable" property is ticked/unticked in the Inspector
Actual results: the "Is Enable" property and all other properties are ticked/unticked in the Inspector
Reproducible with: 2019.3.16f1, 2019.4.3f1, 2020.1.0b15, 2020.2.0a17
Could not test with: 2018.4.25f1
Notes:
1. It is reproducible because Property and PropertyCollection classes have a field "IsEnabled"
2. It is not reproducible when the name of the field "IsEnabled" is changed in Property class or in PropertyCollection class
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note (fix version 2020.2):
The issue has been fixed in 2021.1.0a5
Resolution Note (fix version 2020.2):
fixed in 2020.2.4f1