Bug 90794 - Send to desktop option forgets child-dialogs
Summary: Send to desktop option forgets child-dialogs
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: HI normal
Target Milestone: ---
Assignee: Lubos Lunak
URL:
Keywords:
: 91670 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-10-05 11:34 UTC by Thomas Zander
Modified: 2004-10-19 14:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Zander 2004-10-05 11:34:12 UTC
Version:            (using KDE KDE 3.3.0)
Installed from:    Compiled From Sources

Kwin allows dialogs to stick to their parent if you use the sticky toggle on a window, for that reason I was surprised that sending the parent to another desktop does not make the child follow.

To reproduce:
start konqueror, go to a website
open the find dialog

On the konqueror window use the context menu to send the window to another desktop, using one of your desktops _below_ the 'all desktops' item.

Notice how the parent frame went to the desktop, but the search dialog is still on the current desktop.

I expected the moving of the parent window to move all dialogs as well.
Comment 1 Lubos Lunak 2004-10-12 16:56:17 UTC
CVS commit by lunakl: 

Fix #90794 - make sure dialogs are sent to another virtual desktop
with their mainwindow.
CCMAIL: 90794-done@bugs.kde.org


  M +1 -1      workspace.cpp   1.487


--- kdebase/kwin/workspace.cpp  #1.486:1.487
@@ -1333,5 +1333,5 @@ void Workspace::sendClientToDesktop( Cli
     bool was_on_desktop = c->isOnDesktop( desk ) || c->isOnAllDesktops();
     c->setDesktop( desk );
-    if ( c->desktop() == desk ) // no change or desktop forced
+    if ( c->desktop() != desk ) // no change or desktop forced
         return;
     desk = c->desktop(); // Client did range checking


Comment 2 Lubos Lunak 2004-10-19 14:49:16 UTC
*** Bug 91670 has been marked as a duplicate of this bug. ***