macOS - area dragging causes inconsistent / undesirable behavior #96103

Closed
opened 2022-03-01 13:37:13 +01:00 by Rob van Wees · 4 comments

System Information
Operating system: macOS-12.3-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 580X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.13

Blender Version
Broken: version: 3.1.0 Beta, branch: master, commit date: 2022-02-23 19:16, hash: 88712453f6
Worked: unknown

Short description of error
In Blender, it is possible to drag an area into a separate window with SHIFT-drag. When doing that, the Blender application responds inconsistently between the 'original' and any 'broken-out' window(s).

Start situation: default Blender area setup as in image below
B3.1b - basic area setup.png
After dragging an area outside the Blender window (with SHIFT) held down, I have the following setup:
B31b - Outliner separated.png

At this point, several undesirable things happen:

  • Only one (1) area can be dragged out from the 'main' window. After breaking out the outliner, SHIFT and CTRL key presses are ignored in the original window (3d view).
  • Additional windows can be dragged-out from the broken-out window. Again, one (1) additional window can be broken out. B31b - multiple separations.png
  • The 'original main' window can no longer be activated as per OS visuals/settings. The title bar and buttons stay grayed out as an inactive window would on macOS. Broken-out windows can each be activated properly
  • The broken-out window is always-in-front - similar to an application- or system-modal dialog window would. If there are multiple broken-out windows, each remains always-in-front within their hierarchy / order of breaking out.
  • The last broken-out window can be moved freely, Any of its 'parent' windows cannot; when moving, the underlying hierarcy of windows moves with it.
  • The Quit Dialog box is displayed in the currently 'active' broken-out window. B31b - Outliner separated-quit dialog.png B31b - multiple separations - quit dialog.png The dialog is not fully visible due to the narrow window size.
  • Similarly, when seleting a new area to be displayed, the selection dialog is not fully visible. B31b - Outliner separated - selection dialog.png The selection window cannot be navigated with cursor keys, I have to resize the window for the dialog to fit.
  • In the 'original main' window (here: 3d view), the mouse pointer does not change to a window resize pointer when dragged over the window border of the 3d view window.
  • The mouse pointer does not change to a 'move separation' pointer when dragged over area splits within the window.

Expectation:
I realise that blender is designed to use a Single Document Interface setup. The current behavior, however, is inconsistent, gets unpredictable with multiple windows open and, frankly, annoying to use.

I expect to either:

  • not be able to separate an area into its own window, thereby having the Blender application strictly follow SDI design rules
    or:
  • have any window ('original main' or separated) to conform to OS standards; to be a fully functional window as per OS design rules, not forced-on-top, can be activated, moved separately, etc.
  • have blender mouse pointers to function the same in any of the application's windows
  • have application-modal dialogs to appear in the 'original main' window
  • have any dialog (i.e. area selection, quit) to be fully navigable within the (bounds of the) window it is displayed in

Exact steps for others to reproduce the error

  1. open blender
  2. separate an area into a separate window with SHIFT-drag. Repeat if necessary from each newly separated window.
**System Information** Operating system: macOS-12.3-x86_64-i386-64bit 64 Bits Graphics card: AMD Radeon Pro 580X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.13 **Blender Version** Broken: version: 3.1.0 Beta, branch: master, commit date: 2022-02-23 19:16, hash: `88712453f6` Worked: unknown **Short description of error** In Blender, it is possible to drag an area into a separate window with SHIFT-drag. When doing that, the Blender application responds inconsistently between the 'original' and any 'broken-out' window(s). Start situation: default Blender area setup as in image below ![B3.1b - basic area setup.png](https://archive.blender.org/developer/F12892693/B3.1b_-_basic_area_setup.png) After dragging an area outside the Blender window (with SHIFT) held down, I have the following setup: ![B31b - Outliner separated.png](https://archive.blender.org/developer/F12892696/B31b_-_Outliner_separated.png) At this point, several undesirable things happen: - Only one (1) area can be dragged out from the 'main' window. After breaking out the outliner, SHIFT and CTRL key presses are ignored in the original window (3d view). - Additional windows can be dragged-out from the broken-out window. Again, one (1) additional window can be broken out. ![B31b - multiple separations.png](https://archive.blender.org/developer/F12892719/B31b_-_multiple_separations.png) - The 'original main' window can no longer be activated as per OS visuals/settings. The title bar and buttons stay grayed out as an inactive window would on macOS. Broken-out windows can each be activated properly - The broken-out window is always-in-front - similar to an application- or system-modal dialog window would. If there are multiple broken-out windows, each remains always-in-front within their hierarchy / order of breaking out. - The last broken-out window can be moved freely, Any of its 'parent' windows cannot; when moving, the underlying hierarcy of windows moves with it. - The Quit Dialog box is displayed in the currently 'active' broken-out window. ![B31b - Outliner separated-quit dialog.png](https://archive.blender.org/developer/F12892700/B31b_-_Outliner_separated-quit_dialog.png) ![B31b - multiple separations - quit dialog.png](https://archive.blender.org/developer/F12892732/B31b_-_multiple_separations_-_quit_dialog.png) The dialog is not fully visible due to the narrow window size. - Similarly, when seleting a new area to be displayed, the selection dialog is not fully visible. ![B31b - Outliner separated - selection dialog.png](https://archive.blender.org/developer/F12892705/B31b_-_Outliner_separated_-_selection_dialog.png) The selection window cannot be navigated with cursor keys, I have to resize the window for the dialog to fit. - In the 'original main' window (here: 3d view), the mouse pointer does not change to a window resize pointer when dragged over the window border of the 3d view window. - The mouse pointer does not change to a 'move separation' pointer when dragged over area splits within the window. **Expectation:** I realise that blender is designed to use a Single Document Interface setup. The current behavior, however, is inconsistent, gets unpredictable with multiple windows open and, frankly, annoying to use. I expect to either: - not be able to separate an area into its own window, thereby having the Blender application strictly follow SDI design rules or: - have any window ('original main' or separated) to conform to OS standards; to be a fully functional window as per OS design rules, not forced-on-top, can be activated, moved separately, etc. - have blender mouse pointers to function the same in any of the application's windows - have application-modal dialogs to appear in the 'original main' window - have any dialog (i.e. area selection, quit) to be fully navigable within the (bounds of the) window it is displayed in **Exact steps for others to reproduce the error** 1. open blender 2. separate an area into a separate window with SHIFT-drag. Repeat if necessary from each newly separated window.
Author

Added subscriber: @Robw

Added subscriber: @Robw
Member

Added subscriber: @Harley

Added subscriber: @Harley
Member

This is a duplicate of #92331 (Creating a detached window makes the main window irreversibly loose focus in 2.93.2 +)

This is a duplicate of #92331 (Creating a detached window makes the main window irreversibly loose focus in 2.93.2 +)

Closed as duplicate of #92331

Closed as duplicate of #92331
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#96103
No description provided.