Search Issue Tracker
Fixed
Fixed in 2022.3.58f1, 6000.0.37f1, 6000.1.0b5, 6000.2.0a1, 7000.0.0a17
Votes
0
Found in
2022.3.49f1
6000.0.23f1
6000.1.0a7
6000.2.0a1
7000.0.0a1
Issue ID
UUM-83458
Regression
Yes
The drag line position is not updated after viewData is restored
Steps to reproduce:
1. Create a EditorWindow with a TwoPaneSplitView with two children.
2. Set its viewDataKey to a non null string
3. Runt the Open the created EditorWindow
4. Resize the split view
5. From the window menu (at the top right corner of the window), select the "Reload Window" menu it.
Actual results:
The geometries of the children is restored but the drag line element is at the wrong position.
Expected results:
The geometries of the children is restored and the drag line element is at the right position (right edge of the first child).
Reproducible with versions:
6000.0.23f1
Not reproducible with versions:
Can’t test with versions:
Tested on (OS):
MacOS
Notes:
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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
I could not reproduce the issue.