Switching open windows ignores held modifiers on WIN32 #40059

New Issue

System Information
Win7x64 GTX660M

Blender Version
Broken: 2.70 f93bc76
Worked: (optional)

Short description of error
If multiple windows are open (but same Blender instance), shift+click or ctrl+click on the unfocused one (to pan or zoom in a viewport for instance) will be taken as a simple click instead. It makes working with floating viewports difficult since one must focus the window first, then act.

Exact steps for others to reproduce the error
Pop out a new 3D view by shift-clicking the corner, switch from one to the other using click with any modifier key (ctrl or shift).

**System Information** Win7x64 GTX660M **Blender Version** Broken: 2.70 f93bc76 Worked: (optional) **Short description of error** If multiple windows are open (but same Blender instance), shift+click or ctrl+click on the unfocused one (to pan or zoom in a viewport for instance) will be taken as a simple click instead. It makes working with floating viewports difficult since one must focus the window first, then act. **Exact steps for others to reproduce the error** Pop out a new 3D view by shift-clicking the corner, switch from one to the other using click with any modifier key (ctrl or shift).

Changed status to: 'Open'

Added subscriber: @hadrien

#85112 was marked as duplicate of this issue

#84310 was marked as duplicate of this issue

#76787 was marked as duplicate of this issue

#74684 was marked as duplicate of this issue

#66088 was marked as duplicate of this issue

#60708 was marked as duplicate of this issue

Added subscriber: @ideasman42

I had a fix for this but it broke on ms-windows for some reason.
https://developer.blender.org/T34255

Heres an alternate fix: T40059_fix.diff

... though its a bit odd to handle key-down events differently to key-up events.

I had a fix for this but it broke on ms-windows for some reason. https://developer.blender.org/T34255 Heres an alternate fix: [T40059_fix.diff](https://archive.blender.org/developer/F87434/T40059_fix.diff) ... though its a bit odd to handle key-down events differently to key-up events.

Added subscriber: @mont29

Added subscriber: @ThomasDinges

@ideasman42, why not just go ahead with this fix? otherwise make it a TODO.

@ThomasDinges might be interested in testing it.

@ideasman42, why not just go ahead with this fix? otherwise make it a TODO. @ThomasDinges might be interested in testing it.

Changed status from 'Open' to: 'Resolved'

fixed cb023ce0fd

fixed cb023ce0fd

Changed status from 'Resolved' to: 'Open'

Still happening for me, both on Windows and Fedora.

Does it happen with both 2.75a release and latest builds from builder.blender.org?

Yes, both on Windows and Fedora, release and buildbot.
(Fedora with Wayland if that is relevant)

Yes, both on Windows and Fedora, release and buildbot. (Fedora with Wayland if that is relevant)

Can actually confirm the issue on Debian Jessie + KDE.

@ideasman42, do you have any inputs here?

Can actually confirm the issue on Debian Jessie + KDE. @ideasman42, do you have any inputs here?

I've committed 2 different fixes for this. Both times they caused issues for other users which I couldn't redo,
Infact this has already been reported and moved to TODO (#40155).

The last fix is still in the code, but commented out (fd781c1095)

I wouldn't mind enabling this at the beginning of a release cycle, then spend time/effort to get to the bottom of the problem... test on different platforms... whatever it takes.

For anyone interested to test, uncomment USE_WIN_ACTIVATE define in source/blender/windowmanager/intern/wm_window.c.

See also: #34255 #40317 #40155

I've committed 2 different fixes for this. Both times they caused issues for other users which I couldn't redo, Infact this has already been reported and moved to TODO (#40155). The last fix is still in the code, but commented out (fd781c1095) I wouldn't mind enabling this at the beginning of a release cycle, then spend time/effort to get to the bottom of the problem... *test on different platforms... whatever it takes.* ---- For anyone interested to test, uncomment `USE_WIN_ACTIVATE` define in `source/blender/windowmanager/intern/wm_window.c`. See also: #34255 #40317 #40155

Added subscriber: @JulianEisel

Tried the fix, doesn't work for me :/ (yes, I un-commented USE_WIN_ACTIVATE)

Adding After Release project to increase chance that we won't forget it ;)

Tried the fix, doesn't work for me :/ (yes, I un-commented USE_WIN_ACTIVATE) Adding *After Release* project to increase chance that we won't forget it ;)

Changed status from 'Open' to: 'Archived'

As was mentioned above -- it's a known TODO (http://wiki.blender.org/index.php/Dev:Source/Development/Todo/UserInterface#Events)

Surely improvements are welcome but better to have this happen outside of the bug tracker work. Thanks for the report, but archiving it now.

As was mentioned above -- it's a known TODO (http://wiki.blender.org/index.php/Dev:Source/Development/Todo/UserInterface#Events) Surely improvements are welcome but better to have this happen outside of the bug tracker work. Thanks for the report, but archiving it now.

Closed as duplicate of #60708

Changed status from 'Duplicate' to: 'Open'

Added subscribers: @b4sh-3r, @JacquesLucke

Not sure why's that assigned to me. Was mentioned as a TODO. Is fine if someone looks into this report, but then assign to self. And maybe change type from to a TODO.

Added subscriber: @clepsydrae

I don't mean to "me too"; just wanted to point out that at least for some users (e.g. me) this issue basically breaks using multiple windows due to all the accidental incorrect mouse issues that come from it. The only way I can use Blender multi-monitor is to have one big window stretched across multiple screens, which requires window manager rules to remember the window position, and since the monitors are different sizes, awkward workarounds to handle that, etc. Thanks for any time you have to look at it.

Added subscriber: @Rawalanche

Added subscriber: @SebBlender

Added subscribers: @Parfen, @mano-wii

Added subscriber: @Gilberto.R

Added subscriber: @amgg

Added subscriber: @Harley

I think a complaint like this (and similar) would go away with this on Windows: https://developer.blender.org/D13951, since the target window would (most likely) be focused when moving the mouse there and would therefore get all keyboard input messages.

I don't think changing Window focus on hover is a good idea. The amount of unexpected issues this can cause will compound over time. It's also inconsistent with pretty much most other multi-window software out there. Issue with modifier keys not working on first interaction should be solved specifically, not with a monstrous solution that has many side effects.

This issue was referenced by 8c8c102980

This issue was referenced by 8c8c1029806a790e92973612c3675a81939b518c

Changed status from 'Confirmed' to: 'Resolved'

ALT not working in Blender 3.3
Industry compatible keymap. I hold ALT and tweak with the middle mouse button in different windows. Panning is expected, but sometimes works like moving objects

ALT not working in Blender 3.3 Industry compatible keymap. I hold ALT and tweak with the middle mouse button in different windows. Panning is expected, but sometimes works like moving objects

@Parfen can you make a bug report?

Re-opening this for Windows as 24f3cb9b5c removed support for it.

Although we might consider it a known issue and document it since I'm not sure this can reliably work on Windows at the moment.

Re-opening this for Windows as 24f3cb9b5c1b089b56a9601e175ac9d33a86dda0 removed support for it. Although we might consider it a known issue and document it since I'm not sure this can reliably work on Windows at the moment.

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Switching open windows ignores held modifiers on WIN32 #40059