Keyboard event handling fails to handle multiple Windows without manual focus switching #67192

Closed
opened 2019-07-18 19:50:56 +02:00 by Gavin Scott · 4 comments

System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.25

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-11 13:50, hash: 06312c6d2d
Worked: (optional)

Short description of error
If you have multiple WIndows in one Blender instance, say one on each of two monitors, you have to activate the other window by clicking in it etc. before keyboard events will be delivered to that window instead of the original currently system-focused one, even when you have the mouse over a region in the new window.

Exact steps for others to reproduce the error
Use Window->New Main Window to create a second window (If possible maximize it on a second screen) and switch the new window to Texture Paint.
Move the mouse back and forth over the two windows and note that mouse tracking is appropriately highlighting things etc.
Click on the texture area in the new window and use SHIFT+F to resize the brush and note its behavior is correct there.
Move the mouse back over the first window and press SHIFT+F and the event tries to go to the original window which will either show the size gizmo at the edge of the window (if the last mouse track event in that window was still over the texture area) or not act on it at all.
Or try using a command over the original window that would be appropriate there and it does not get delivered as the second window has the sole focus for keyboard events.

I would think this could be made better such that we can figure out which region on which window has the pointer and get the keyboard events to the right place without needing to manually activate each window first. It's rather a substantial limitation in the otherwise amazing 2.80 multiple-window support.

On Linux the same behavior is reported. There you might be able to use mouse focus mode in the window manager as a workaround, though that's less than ideal for people whom mouse focus drives insane :)

I don't know what the Mac behavior is.

I imagine this isn't the easiest thing to handle in a cross-platform manner.

**System Information** Operating system: Windows-10-10.0.17134 64 Bits Graphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.25 **Blender Version** Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-11 13:50, hash: `06312c6d2d` Worked: (optional) **Short description of error** If you have multiple WIndows in one Blender instance, say one on each of two monitors, you have to activate the other window by clicking in it etc. before keyboard events will be delivered to that window instead of the original currently system-focused one, even when you have the mouse over a region in the new window. **Exact steps for others to reproduce the error** Use Window->New Main Window to create a second window (If possible maximize it on a second screen) and switch the new window to Texture Paint. Move the mouse back and forth over the two windows and note that mouse tracking is appropriately highlighting things etc. Click on the texture area in the new window and use SHIFT+F to resize the brush and note its behavior is correct there. Move the mouse back over the first window and press SHIFT+F and the event tries to go to the original window which will either show the size gizmo at the edge of the window (if the last mouse track event in that window was still over the texture area) or not act on it at all. Or try using a command over the original window that would be appropriate there and it does not get delivered as the second window has the sole focus for keyboard events. I would think this could be made better such that we can figure out which region on which window has the pointer and get the keyboard events to the right place without needing to manually activate each window first. It's rather a substantial limitation in the otherwise amazing 2.80 multiple-window support. On Linux the same behavior is reported. There you might be able to use mouse focus mode in the window manager as a workaround, though that's less than ideal for people whom mouse focus drives insane :) I don't know what the Mac behavior is. I imagine this isn't the easiest thing to handle in a cross-platform manner.
Author

Added subscriber: @GavinScott

Added subscriber: @GavinScott

Added subscriber: @brecht

Added subscriber: @brecht

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Brecht Van Lommel self-assigned this 2019-07-19 12:42:25 +02:00

That's just how it works now, certainly something that can be improved but not a bug.

That's just how it works now, certainly something that can be improved but 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
2 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#67192
No description provided.