Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2022.1
2022.2
2022.2.0a10
Issue ID
1425239
Regression
Yes
[UIToolkit] TrackPropertyValue isn't called more than once when changing property value in one window instance
How to reproduce:
1. Open the user's attached "2022 testing" project
2. Open the "SampleScene" Scene
3. Select the "Testy" GameObject in the Hierarchy
4. Change the "Change Me" value twice in the Inspector
5. Observe the value below the "Change me" field
Expected result: Value set right to the "Change Me" field matches the value below the field
Actual result: After changing the "Change Me" value for the second time, the value below the field isn't updated
Reproducible with: 2022.1.2f1, 2022.2.0a12
Not reproducible with: 2021.3.4f1, 2022.2.0a13, 2022.2.0a15
Couldn't test with: 2019.4.39f1, 2020.3.35f1 (project isn't compatible)
Reproduced on: MacOS 12.3 (Intel)
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a13