Search Issue Tracker
Fixed
Fixed in 2021.3.24f1, 2022.2.19f1, 2023.1.0b13, 2023.2.0a10
Votes
0
Found in
2023.1.0a6
2023.2.0a1
Issue ID
UUM-1589
Regression
No
[Linux] DisplayInfo.WorkArea ignores resolution scaling when working with multiple displays
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. Enter Windowed mode
6. Move the Player window to the secondary screen
7. Press the "Snap to bottom right" button
Expected results: Player window snaps to the bottom of the secondary screen regardless of the resolution scaling used
Actual results: Player window does not snap to the bottom of the screen, ignoring the applied resolution scaling
Reproducible with: 2021.2.0a16, 2021.2.0b5, 2022.1.0a4
Couldn't test with versions older versions as MoveWindowAPI was introduced in 2021.2.0a16
Notes:
1. A 4K primary display with 200% resolution scaling and a 1080p secondary display were used for testing
2. Tested on Ubuntu 20.04
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
Add comment