Switching between workspaces is glitching when using monitors with different dpi #74160

Closed
opened 2020-02-24 11:41:06 +01:00 by Marcin Twarowski · 7 comments

System Information
Operating system: Windows-10-10.0.16299-SP0 64 Bits
Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86

Blender Version
Broken: version: 2.83 (sub 4), branch: master, commit date: 2020-02-23 23:00, hash: abb7364912

Short description of error
When using Blender on two monitors with different DPI, header menus will disappear when switching between workspaces. Also UI scale doesn't refresh properly.

Exact steps for others to reproduce the error
different_ui_scales_bug.blend

  • In Windows 10 set custom scale on the second monitor in Display Settings > Scale and Layout, for example to 175%, so that each monitor has different scale.
  • Put one Blender window on each monitor (same Blender session).
  • Switch between different workspaces tabs.

Blender [C__Users_TwaMa_Desktop_different_ui_scales_bug.blend] 24.02.2020 11_39_17.mp4

**System Information** Operating system: Windows-10-10.0.16299-SP0 64 Bits Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86 **Blender Version** Broken: version: 2.83 (sub 4), branch: master, commit date: 2020-02-23 23:00, hash: `abb7364912` **Short description of error** When using Blender on two monitors with different DPI, header menus will disappear when switching between workspaces. Also UI scale doesn't refresh properly. **Exact steps for others to reproduce the error** [different_ui_scales_bug.blend](https://archive.blender.org/developer/F8366166/different_ui_scales_bug.blend) - In Windows 10 set custom scale on the second monitor in **Display Settings > Scale and Layout**, for example to 175%, so that each monitor has different scale. - Put one Blender window on each monitor (same Blender session). - Switch between different workspaces tabs. [Blender [C__Users_TwaMa_Desktop_different_ui_scales_bug.blend] 24.02.2020 11_39_17.mp4](https://archive.blender.org/developer/F8366157/Blender__C__Users_TwaMa_Desktop_different_ui_scales_bug.blend__24.02.2020_11_39_17.mp4)

Added subscriber: @MarcinTwarowski

Added subscriber: @MarcinTwarowski
Member

Added subscribers: @Harley, @EAW

Added subscribers: @Harley, @EAW
Member

@Harley Is this the type of bug you said to watch for in D6370?

@Harley Is this the type of bug you said to watch for in [D6370](https://archive.blender.org/developer/D6370)?
Member

@EAW - @Harley Is this the type of bug you said to watch for in D6370?

No, the Windows 10 feature addressed in that patch (when working correctly) only affects the non-client area (the titlebar surrounding blender). When dragging a window from one window to another one with a different DPI setting that outer titlebar will change height to match. When NOT working correctly (caused only by using an old Intel driver), then the mouse pointer differs from where it operates by a distance equal to that vertical size change in the titlebar.

This issue doesn't seem to be at all related, but I'm not sure what this is. I always wonder if we'll have trouble caused by us storing monitor dpi globally instead of by monitor.

> @EAW - @Harley Is this the type of bug you said to watch for in [D6370](https://archive.blender.org/developer/D6370)? No, the Windows 10 feature addressed in that patch (when working correctly) only affects the non-client area (the titlebar surrounding blender). When dragging a window from one window to another one with a different DPI setting that outer titlebar will change height to match. When NOT working correctly (caused only by using an old Intel driver), then the mouse pointer differs from where it operates by a distance equal to that vertical size change in the titlebar. This issue doesn't seem to be at all related, but I'm not sure what this is. I always wonder if we'll have trouble caused by us storing monitor dpi globally instead of by monitor.

Closed as duplicate of #72838

Closed as duplicate of #72838

Added subscriber: @MirekDusin

Added subscriber: @MirekDusin

This comment was removed by @MirekDusin

*This comment was removed by @MirekDusin*
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#74160
No description provided.