Steps to reproduce:
1 create an action for an application to start on desktop 1
2 (re)start openbox
3 start netwmpager (or start it via autostart.sh)
4 switch to desktop 2 by any means you like
5 start the app
-> app is started and placed on desktop 1
So far, everything is nice
6 Now click on desktop 1 (inside netwmpager), inside the window of the app just started
-> The app is moved from desktop 1 to desktop 2, the user view is not changed.
What I'd expect (and how it works with all the stable releases up to and including 3.4.6.1) is that the user view is switched to desktop 1 and all apps remain where they are.
If you need any more info, I'm also available as Blackb|rd on oftc and Freenode.
I presume you're rferring to this:
* Change _NET_ACTIVE_WINDOW messages to not change the current desktop, but to bring the window to the current desktop instead. This is the industry standard policy
So what *should* netwmpager be doing instead of using _NET_ACTIVE_WINDOW? Currently, I can't reach the netwmpager author, but I might be able to hack together a patch given a few pointers.
the general concensus of other applications is that if you want to show a window on another desktop, you switch desktops, then activate that window. so it would do a _NET_CURRENT_DESKTOP then _NET_ACTIVE_WINDOW or somesuch.
This is something I plan to take up with the other EWMH people, but the current behavior of _NET_ACTIVE_WINDOW won't change I don't think.
Created attachment 1717[details]
Desktop switching fix
For completeness, here's a one-line patch to fix netwmpgaer-1.11. I'll contact the author to get it included in future versions. As far as I can tell, using this (patched) netwmpager with older OpenBox releases (or other NETWM managers) should pose no problems.
Created attachment 1717 [details] Desktop switching fix For completeness, here's a one-line patch to fix netwmpgaer-1.11. I'll contact the author to get it included in future versions. As far as I can tell, using this (patched) netwmpager with older OpenBox releases (or other NETWM managers) should pose no problems.