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 75758 - window open on the workspace where launched.
window open on the workspace where launched.
Status: RESOLVED FIXED
Product: metacity
Classification: Other
Component: general
unspecified
Other other
: Normal enhancement
: GNOME2.x
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2002-03-21 15:34 UTC by kz
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description kz 2002-03-21 15:35:11 UTC 
Package: metacity
Severity: enhancement
Version: 2.3.55
Synopsis: window open on the workspace where launched.
Bugzilla-Product: metacity
Bugzilla-Component: general

Description:
now,  metacity has four default workspaces. and I found it's useful. :)
but I think there's missing part.

for my turtle box, big monster like galeon waste long long time to
launch.
and I have to wait until the window open on intended workspace.
yeah, there's a workaround to move to another place after open
wherever.
but it is just *workaround*.

do you think that's possible to set the accurate workspace number to
open?
like use of DISPLAY variable to set where to open, :0, :1, so on.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-03-21 10:35 -------

Reassigning to the default owner of the component, hp@redhat.com.
Comment 1 Havoc Pennington 2002-03-21 16:35:52 UTC 
This should be done as part of application launch feedback.
Most of the work is not in the window manager.
Comment 2 kz 2002-03-21 16:56:03 UTC 
hm... not window manager?... well, then
where should I have to post this issue to fire up?
Comment 3 Havoc Pennington 2002-03-21 17:28:26 UTC 
It's already fired up, it's a well-known issue. Will be worked on
right after GNOME 2.
Comment 4 kz 2002-03-21 17:50:36 UTC 
ok. waiting...
Comment 5 Luis Villa 2002-05-30 23:15:15 UTC 
Enhancement, then, since we don't have a 'pre-2.2' miletone or
something like that.
Comment 6 Havoc Pennington 2003-02-22 22:23:20 UTC 
This is done now, when startup notification is used. 
(If you get a busy cursor on launching the app, you should also 
see this behavior working.)