| Issue 36: | Main instance does not focus when starting new instance (using Metacity) | |
| 1 person starred this issue and may be notified of changes. | Back to list |
What steps will reproduce the problem? 1. Start Glista 2. Start another Glista What is the expected output? What do you see instead? The already running instance of Glista should be brought on top and gain focus, instead the URGENT window manager hint is set and the entry in the window list flashes but the window is not brought on top and focused. However, it does work like it's supposed to when using Compiz. I'm not sure if this is an issue with Glista, libunique or Metacity itself and thought I'd start here with reporting it. If you want me to move this somewhere else I'll be happy to do so. Regretfully I haven't even been able to workaround it using Devil's Pie (which has a (focus) command but that doesn't bring the window on top). What version of the product are you using? On what operating system? 0.4 under Ubuntu 8.10 (Intrepid) Thanks for this little gem by the way :-) |
|
,
Apr 05, 2009
I forgot to post links to some possibly relevant issues: https://bugs.launchpad.net/metacity/+bug/197288 https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/9839 |
|
,
Apr 06, 2009
Someone pointed me to a relevant discussion on the Metacity blog: http://blogs.gnome.org/metacity/2008/10/20/by-these-presents/ At least the version Metacity included with Ubuntu 8.10 right now prevents windows from being summoned/presented/raised when it didn't previously have the focus. I'll take a look at any custom patches being applied later (probably just by apt-get sourcing the relevant package). So adjusting the steps to reproduce: 1. Start Glista 2. Focus Firefox or some other application 3. Start another Glista Result: Glista is not summoned/presented/raised. While thinking about this a few things came to mind (some of this is brought up in the blog post I mentioned before): * As Havoc pointed out a global switch makes no sense at all, "Do you want to break Firefox, or Pidgin?". * Allowing applications to decide themselves without a users permission whether or not a particular window should be summoned or pulse when present is called is probably not wise to do since it might pose a security hazard (see: https://bugzilla.redhat.com/show_bug.cgi?id=138453). However, I'm thinking at the very least it would be quite useful if applications could indicate the mode they wish to (summon, pulse etc.). I'd also say that a user should be able to flip the global switch to enable this behavior. * Allowing a user to easily allow/deny/change this behavior per window type for some reason sounds like a good idea to me, but it seems it's quite difficult to realize in the real world (see: http://blogs.gnome.org/metacity/2008/11/02/window-matching/). All I know is that I want to be able focus applications easily so I can quickly bring them up to do task X (such as adding new tasks in the case of Glista). Currently I'm just wondering what GNOME Do does since they manage to always focus the application when a user presses the summon keybinding. (Also, not directly relevant to this report, it would probably be a good idea to actually toggle the visibility instead of always focusing it. That way you can use Metacity's keybinding functionality to start a Glista instance and use it for quickly hiding it too. See: https://bugs.launchpad.net/gtimelog/+bug/356495) |
|
 Sign in to add a comment
|
