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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a13