Search Issue Tracker
Fixed
Fixed in 2022.1.18f1, 2022.2.0b5, 2023.1.0a3
Unknown (hidden) 2022.2.X
Votes
0
Found in
2022.1.0b13
2022.2.0a8
2023.1.0a1
Issue ID
UUM-3480
Regression
No
Inconsistent styling of Treeview Items between IMGUI and UI Toolkit
How to reproduce:
1. Open the attached "2022.1" project (UI Toolkit)
2. Open the Sequence Assets window (Window -> Sequencing -> Sequence Assets)
3. Note the size of the Left-Side padding
4. Open the attached "2020.3" project (IMGUI)
5. Open the Sequences window (Window -> Sequencing -> Sequences)
Expected result: Consistent padding size
Actual result: Padding is bigger in UI Toolkit than in IMGUI
Reproducible with: Sequences 2.0.0-pre.1 (2022.1.0b13, 2022.2.0a8) - using 1.0.0-preview.18 UI Toolkit
Not reproducible with: Sequences 1.1.0 (2020.3.31f1, 2022.1.0b13, 2022.2.0a8) - using IMGUI
Note:
- The Sequences package was used since it is easier and visually clearer in reproducing the issue
- The issue is in UI Toolkit since 1.1.0 used IMGUI and 2.0.0-pre.1 used UI Toolkit
- In 1.1.0, the Sequences window has two panels (Structure and Asset Collection). In 2.0.0-pre.1, these panels are now separated into two distinct windows. Sequences and Sequence Assets.
- 2.0.0-pre.1 only works in 2022.1 and higher
- 1.1.0 only works in 2020.3 and higher
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
- Bad performance when executing the Physics.IgnoreCollisions() method while in Play Mode
- Sprite Editor has a thicker separator between buttons when "Sprite Editor" option is selected
- "NullReferenceException: Object reference not set to an instance of an object" error is thrown when UpdateVolumeStack function is called
- [Windows] Unicode custom text input window shows question marks when inserting an emoji
- Memory leak when the VFX Graph Editor is open
Resolution Note (fix version 2023.1.0a3):
Fixed in: 2023.1.0a3
Resolution Note (fix version 2022.2.0b5):
Fixed in: 2022.2.0b5
Resolution Note (2022.2.X):
Created by mistake
Resolution Note (fix version 2022.1.18f1):
Fixed in: 2022.1.18f1