Stop moving mouse between monitors to "steal" focus

[sound-friend]

Is your feature request related to a problem? Please describe.
not sure if this is intended behaviour, but it's aggravating when i have multiple monitors that when i switch between them, my focus is automatically switched to that monitor and the last window open. i typically select an item to copy, and copy it as i'm moving to the other monitor. this makes me miss a lot of copies, as well as other motions.

Describe the solution you'd like
a togglable switch to "change focus to current monitor only when clicked"

i didn't see a current option in there, but if there is, i'll close this issue. thanks for such an innovative way of managing the desktop?

[jtaala]

Unfortunately, this is a constraint for implementing for "per monitor workspaces" (note: gnome doesn't do per monitor workspaces). You can read about this constraint here #389 (comment).

Closing this issue as a duplicate of #389.

In short, the only way to disable this would be to not do "per monitor workspaces" (and would mean a pretty much a rewrite / reimplementation of many paperwm concepts). Unfortunately, multi-monitor support still has issues in PaperWM (and is currently paperwm's archilles heel). Interestingly, this was one of the reasons (gnome, or more specifically mutter, workspace/monitor constraints) niri dev was started.

Closing as duplicate of #389.

[sound-friend]

wow, i didnt realize how complicated this issue was! thanks for that! ill investigate further and try to adapt my workflow to account for this barrier.

…

On Sat, Aug 24, 2024, 12:14 AM jtaala ***@***.***> wrote: Unfortunately, this is a constraint for implementing for "per monitor workspaces" (note: gnome doesn't do per monitor workspaces). You can read about this constraint here #389 (comment) <#389 (comment)>. Closing this issue as a duplicate of #389 <#389>. In short, the only way to disable this would be to not do "per monitor workspaces" (and would mean a pretty much a rewrite / reimplementation of many paperwm concepts). Unfortunately, multi-monitor support still has issues in PaperWM (and is currently paperwm's archilles heel). Interestingly, this was one of the reasons (gnome, or more specifically mutter, workspace/monitor constraints) niri dev was started. Closing as duplicate of #389 <#389>. — Reply to this email directly, view it on GitHub <#933 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFEIQW7RRPURBESEJEUMTHLZTACD3AVCNFSM6AAAAABNA3E4M6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBYGA2TANZVHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jtaala]

Well, it's still something that we hope will be addressed in gnome itself (in which case we can align with gnome instead of fighting it). We've just had no luck here - I've actually considered forking a simpler paperwm which doesn't do "per monitor workspaces" - which would alleviate/resolve these multi-monitor issues, but would make paperwm work very differently (the good parts) for multi-monitors.

[sound-friend]

interesting. quick question: with the gnome using one workspace for all monitors, how does that work if there's an option for "workspaces on primary display only"? from a naive interpretation, it seems that that mode would have to be on separate workspaces, one for the primary, and one for the rest.

…

On Sat, Aug 24, 2024, 12:24 AM jtaala ***@***.***> wrote: Well, it's still something that we hope will be addressed in gnome itself (in which case we can align with gnome instead of fighting it). We've just had no luck here - I've actually considered forking a simpler paperwm which doesn't do "per monitor workspaces" - which would alleviate/resolve these multi-monitor issues, but would make paperwm work very differently (the good parts) for multi-monitors. — Reply to this email directly, view it on GitHub <#933 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFEIQW4OFHG2CYICRQXDQVLZTADIZAVCNFSM6AAAAABNA3E4M6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBYGA3DGOBVGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jtaala]

Well, a workspace in mutter is just a logical grouping of windows.

Essentially, in primary display only, when "switching" workspaces, windows on the non-primary are changed to the same grouping when any workspace is activated (i.e. coming out of overview or when "switching workspace"), e.g. with functions like metaWindow.change_workspace.

So, when a workspace is activated, all windows (across monitors) are on the same workspace (or logical grouping) again. Once out of overview etc, you can drag them across monitor boundaries, like it's one big workspace (because it is), e.g. one workspace across monitors (normal gnome behaviour).

You can see/check this by using looking glass (alt+f2) and selecting different windows on the different monitors and running .get_workspace().index() (in the evaluator) on those windows (metaWindow) - you'll see they're all actually on the same workspace index no matter what workspace to switch to.