Strange behaviour with 2 windows/monitor set up in 2.93 #90245

Closed
opened 2021-07-27 17:40:38 +02:00 by Vitória Litwinczyk · 8 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11

Blender Version
Broken: version: 2.93.1, branch: master, commit date: 2021-06-22 05:57, hash: 1b8d33b18c
Worked: version: 2.91.2, branch: master, commit date: 2021-01-19 16:15, hash: 5be9ef4177

Short description of error
Issues when changing windows between monitors, minimizing/maximizing the main window

startup and userpref 2-91.7z

startup and userpref 2-93.7z

startup and userprefs.7z

Exact steps for others to reproduce the error
In 2.91, the windows act as expected:

  • Changing them between monitors moves the taskbar icon between them right away

  • Minimizing one does not minimize the other

  • Clicking on the main window does not bring the secondary window into focus, allowing for the use of other programs on the second monitor, for instance, a browser open with reference images.

In 2.93.1, the behaviour is not as expected:

  • Changing windows between monitors works, but the taskbar icons remain on the monitor they were previously on

  • Minimizing the main window also minimizes the secondary, maximizing the main window also maximizes the secondary window, but it comes back smaller on the screen. The opposite is not true, minimizing the secondary window only affects the secondary window.

  • Using the main window forces the secondary window back into focus if it is on the second monitor, not allowing for the use of other programs on the secondary monitor. The opposite is not true, the secondary window does not force the primary back into focus.

  • Fiddling with the taskbar icons (clicking on them repeatedly) eventually sends the window's taskbar icon to the appropriate monitor

The attached files include the start up file and userpref of both versions in which this has been tested.

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11 **Blender Version** Broken: version: 2.93.1, branch: master, commit date: 2021-06-22 05:57, hash: `1b8d33b18c` Worked: version: 2.91.2, branch: master, commit date: 2021-01-19 16:15, hash: `5be9ef4177` **Short description of error** Issues when changing windows between monitors, minimizing/maximizing the main window [startup and userpref 2-91.7z](https://archive.blender.org/developer/F10241167/startup_and_userpref_2-91.7z) [startup and userpref 2-93.7z](https://archive.blender.org/developer/F10241168/startup_and_userpref_2-93.7z) [startup and userprefs.7z](https://archive.blender.org/developer/F10241170/startup_and_userprefs.7z) **Exact steps for others to reproduce the error** In 2.91, the windows act as expected: - Changing them between monitors moves the taskbar icon between them right away - Minimizing one does not minimize the other - Clicking on the main window does not bring the secondary window into focus, allowing for the use of other programs on the second monitor, for instance, a browser open with reference images. In 2.93.1, the behaviour is not as expected: - Changing windows between monitors works, but the taskbar icons remain on the monitor they were previously on - Minimizing the main window also minimizes the secondary, maximizing the main window also maximizes the secondary window, but it comes back smaller on the screen. The opposite is not true, minimizing the secondary window only affects the secondary window. - Using the main window forces the secondary window back into focus if it is on the second monitor, not allowing for the use of other programs on the secondary monitor. The opposite is not true, the secondary window does not force the primary back into focus. - Fiddling with the taskbar icons (clicking on them repeatedly) eventually sends the window's taskbar icon to the appropriate monitor The attached files include the start up file and userpref of both versions in which this has been tested.

Added subscriber: @Vitoria

Added subscriber: @Vitoria
Member

Added subscribers: @Harley, @PratikPB2123

Added subscribers: @Harley, @PratikPB2123
Member

It is by design I guess. Changes were made on window management for 2.93 release
(refer: https://wiki.blender.org/wiki/Reference/Release_Notes/2.93/User_Interface#Window_Management)

@Harley , can you take a look at the report? Not sure but possibly this behavior is intentional.

It is by design I guess. Changes were made on window management for 2.93 release (refer: https://wiki.blender.org/wiki/Reference/Release_Notes/2.93/User_Interface#Window_Management) @Harley , can you take a look at the report? Not sure but possibly this behavior is intentional.

This is unfortunate in that case, this new management style is frustrating and counter productive. Is there any way to change this in the settings? If not, I think this should be added as a feature to the next release.

Perhaps this new system is better for single monitors with multiple windows, but it is quite terrible for multi window multi monitor.

This is unfortunate in that case, this new management style is frustrating and counter productive. Is there any way to change this in the settings? If not, I think this should be added as a feature to the next release. Perhaps this new system is better for single monitors with multiple windows, but it is quite terrible for multi window multi monitor.
Member

It’s by design, but there is enough flexibility that you can probably get what you want.

The main blender window creates child windows that can each be individually minimized. But they are grouped together and will all minimize if you minimize the parent. This is convenient in many scenarios and was long requested by users who work with many windows at once since they no longer have to minimize each one to do something else.

But if you create a window with “window / new main window” you will create a new separate parent window that is not grouped, will not minimize when you minimize other main windows, and it can have its own children if you want. Basically it will behave exactly as you are used to. And you have can have any number of main windows, each with children, arranged any way you like.

This was a part of many changes to do with window creation on Windows, mostly to properly handle multiple windows on multiple monitors.

It’s by design, but there is enough flexibility that you can probably get what you want. The main blender window creates child windows that can each be individually minimized. But they are grouped together and will all minimize if you minimize the parent. This is convenient in many scenarios and was long requested by users who work with many windows at once since they no longer have to minimize each one to do something else. But if you create a window with “window / new **main** window” you will create a new separate parent window that is not grouped, will not minimize when you minimize other main windows, and it can have its own children if you want. Basically it will behave exactly as you are used to. And you have can have any number of main windows, each with children, arranged any way you like. This was a part of many changes to do with window creation on Windows, mostly to properly handle multiple windows on multiple monitors.

Well, that'll work well enough. Thank you for your time.

Well, that'll work well enough. Thank you for your time.
Member

Changed status from 'Needs Triage' to: 'Archived'

Changed status from 'Needs Triage' to: 'Archived'
Member

Closing as this is expected behavior.

For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Closing as this is expected behavior. For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug
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
3 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#90245
No description provided.