After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 328078 - Extended activation spec
Extended activation spec
Status: RESOLVED OBSOLETE
Product: metacity
Classification: Other
Component: general
trunk
Other Linux
: Normal enhancement
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks: 340691
 
 
Reported: 2006-01-21 21:09 UTC by Elijah Newren
Modified: 2020-11-07 12:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Elijah Newren 2006-01-21 21:09:24 UTC 
Lubos had a proposal for having activation messages optionally (or at least, I wanted to make it optional) specify whether the window should be taken to the user (current behavior for Metacity) or whether the user should be taken to the window (current behavior for KWin; also hacked into the libwnck selector (& tasklist if the appropriate option is set) via different means).  In addition to being useful for pagers, there might also be good uses for apps as well (see bug 153620).  http://mail.gnome.org/archives/wm-spec-list/2005-August/msg00000.html seems to be what I can find at the moment.

One thing to note is that window.c:window_activate checks for leaving show_desktop mode before doing the workspace switching, which order would need to be reversed for the new kind of activation.
Comment 1 André Klapper 2020-11-07 12:35:22 UTC 
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all
old feature requests in Bugzilla which have not seen updates for many years.

If you still use metacity and if you are still requesting this feature in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/metacity/-/issues/

Thank you for reporting this issue and we are sorry it could not be implemented.