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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a13