Newly mapped windows should be displayed when ioncore.set switchto property is true. This does not work for applications started from a shell window, as it used to do with ion3.
Jep, indeed easy to reproduce. Definitely something that needs to be fixed. Not sure when I'll find time though - any further hints appreciated of course :).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It occured when the current window does have the _NET_WM_USER_TIME property set, and the new window doesn't.
Frankly it is unclear to me how this logic should work at all. I've removed the faulty logic, and now we only deny new windows from getting the focus when they explicitly set their _NET_WM_USER_TIME to '0'.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Added this turnaround in my init file:
ioncore.get_hook("clientwin_mapped_hook"):add(function(cwin) cwin:goto() end)
But the bug is still hidden somewhere of course...
I'm not exactly sure how to reproduce this. when i type 'xterm' in an xterm, an xterm is opened and the newly opened xterm gets the focus.
Can you give me some more direct steps to reproduce this bug?
I do notice when starting swing applications from eclipse, those are not switched to.
Starting an xterm from an xterm effectively works.
Starting an xterm (or firefox, or emacs...) from a gnome-terminal does not work...
Jep, indeed easy to reproduce. Definitely something that needs to be fixed. Not sure when I'll find time though - any further hints appreciated of course :).
Looks like this has been like this since commit http://notion.git.sourceforge.net/git/gitweb.cgi?p=notion/notion;a=commit;h=2f8f8bef1817269b460a36dbdeeaaa475200f745
It occured when the current window does have the _NET_WM_USER_TIME property set, and the new window doesn't.
Frankly it is unclear to me how this logic should work at all. I've removed the faulty logic, and now we only deny new windows from getting the focus when they explicitly set their _NET_WM_USER_TIME to '0'.
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).