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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a13