Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X, 2020.3.X
Votes
6
Found in
2019.3
2019.4
2020.1
2020.1.0b13
2020.2.0a4
Issue ID
1258663
Regression
Yes
[Linux] Editor doesn't restore window scale when loading saved layouts
How to reproduce:
1. Create a new project
2. In the Editor switch to the "Default" layout using the dropdown in the top right of the Editor window
3. Grab and drag the right side of the Hierarchy window as far left as it can go
4. Save the new layout as "Test" by going to the layout dropdown and selecting "Save Layout..."
5. Load the "Test" layout
6. Observe the horizontal scale of the Hierarchy window
Expected result: The scale of the Hierarchy window didn't change
Actual result: The Hierarchy window is wider
Reproducible with: 2019.3.16f1, 2019.4.2f1, 2020.1.0b14, 2020.2.0a4, 2020.2.0a16
Not reproducible with: 2018.4.24f1, 2019.3.15f1, 2020.2.0a3
Note: Tested on Ubuntu 18.04 and Windows 10 (Doesn't reproduce)
Comments (1)
-
Peter77
Jul 03, 2020 15:31
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
- “Frame Debugger On” text color not maintained across different Editor Themes in toolbar
- Rendering artefacts appear in the Game view window when maximizing/minimizing Inspector window and Frame Debugger is Enabled
- Threads dropdown in the Profiler is not scrollable even when not all options in the list are visible
- Memory leak when a lot of Particle Systems instantiated while Profiler is open
- "ArgumentOutOfRangeException" error is thrown when trying to delete letters from an RTL TextField when using the Advanced Text Generator
Resolution Note (fix version 2020.2):
Loading saved layouts will restore tab proportions. Also, Unity will now remember the correct size and maximized state when restarting the Editor.
Fixed in 2021.2.0a15
Resolution Note (fix version 2020.3):
Fixed in 2020.3.36f1
Resolution Note (fix version 2020.1):
Fixed in 2020.1.13f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.17f1