GNOME Bugzilla – Bug 75272
Properties Dialog Box is not opening properly in the Work space switcher Applet
Last modified: 2009-08-16 15:13:28 UTC
Desc :Properties Dialog Box is not opening properly in the Work space switcher Applet Build : Solaris 8(sparc) 32-bit with Gnome2.0 Beta 2 Package : gnome2-Control-center Steps to reproduce the problem: 1.Launch an Work space Switcher Applet . 2.move to the second or third workspace 3.Select properties . The properties dialog always opening in the first workspace (workspace 0) only . Actual Results: The properties dialog box is opened in the workspace o. Expected Results: The properties dialog box should be opened in the current workspaceshould be selected How often does this happen? Always.
Hrm; this works here with snaps from CVS. Could you confirm that it is still happening in CVS for you, sekhar?
I can reproduce this .... The steps are 1) Open dialog in workspace A 2) Close if 3) Move to workspace B 4) it opens in workspace A
This is a sawfish bug ... gtk_window_present/gdk_window_focus doesn't move the window to the current desktop with sawfish see gtkwindow.c:gtk_window_present works fine with metacity
gtk_window_present works fine for me - sawfish switches to the desktop containing the window
This is gtk_window_present on a hidden window ... the window should get shown in the current workspace, instead it gets shown in the workspace in which it as last shown
says who? This behaviour seems to be unspecified by the wm-spec (I'm not saying that sawfish's behaviour is necessarily the right thing in all cases, I'm trying to point out this issue isn't as clear cut as you seem to think) imho, if the application wants to ensure it appears on the current workspace, the only 100% solution is to do that explicitly
Sure, it may be a grey area. That's fair enough. But I know which side of the grey are I'd prefer sawfish to err on :-)
I don't think that any one application can dictate how it wants the spec to be interpreted. It should work with all possibly interpretations
*** Bug 83140 has been marked as a duplicate of this bug. ***