Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.1
2022.1
2022.1.0a4
Issue ID
1355375
Regression
No
[Linux] DisplayInfo.WorkArea excludes the Top Bar area for Secondary screen
How to reproduce:
1. Open the attached project named "desktop-move-window-sample-main.zip"
2. Open "SampleScene"
3. Build and Run
4. Press the ESC key
5. Move the Player window to the secondary screen
6. Press the "Snap to top left" button
Expected results: The player window snaps to the top corner of the screen
Actual results: The player window snaps under the excluded area which would be used for the Linux Top Bar if the screen was a Primary one
Reproducible with: 2021.2.0a16, 2021.2.0b5, 2022.1.0a4
Couldn't test with older versions as MoveWindowAPI was introduced in 2021.2.0a16
Notes:
1. Tested with a 4K Primary display and a 1080p secondary display
2. The reported area statistic also reflects the fact 54px are excluded from the WorkArea height on a 1080p secondary screen
3. The issue occurs regardless of resolution scaling applied
4. The Player window can be moved to the excluded area manually and docked in the top left corner that way
5. Tested on Ubuntu 20.04
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
- Element name field has no character limit in UI Builder
- Async method in Play Mode being aborted when calling `new System.Windows.Forms.Form`
- Animator window Eye button on click visual does not cover the whole area of the button when clicked
- Frame Debugger scrollbar gets cut off at the bottom when the Frame Debugger window is maximised
- Frame Debugger docked with the Game View can still be enabled when Game View is maximised and minimised
Resolution Note (2022.2.X):
This is a current limitation of X. Our player does not require any particular window manager, just X11. X11 treats the work area as one large virtual space, so the bars extend across both as there is only a single rect.