Bug 196137

Summary: Do not raise window on drag operation
Product: [Plasma] kwin Reporter: Dotan Cohen <kde-2011.08>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: donn.ingle, finex, kde-2011.08, thomas.luebking
Priority: NOR    
Version: 4.2.4   
Target Milestone: ---   
Platform: Ubuntu   
OS: Unspecified   
Latest Commit: Version Fixed In:

Description Dotan Cohen 2009-06-12 09:07:39 UTC 
Version:            (using KDE 4.2.4)
Installed from:    Ubuntu Packages

In general, I dislike the automatic focus mechanisms and prefer focus on mouse click only. However, when dragging icons it is often helpful to leave the windows as they appear on the screen. I propose an option for _not_ raising a window on drag operations be added to KDE.

Usage example:
Open a Kmail composer window and a Dolphin window, such that the compose window overlaps the Dolphin window but show some icons below. Start dragging an icon into the composer window. Boom! The compose windows disappears under the Dolphin window. This is annoying.

Note that KDE 3 could be configured to not raise windows on drag, as this bug describes.
Comment 1 Christoph Feck 2009-06-12 16:20:21 UTC 
The window raising could happen only on mouse release and unless you initiated a drag inside the window.

Reassigning.
Comment 2 Donn Ingle 2009-06-12 17:46:09 UTC 
I also depended on this behaviour in KDE 3.5 -- I think I must have set it up via window/application settings (I can't recall). An easy tickbox for "Do not raise windows that start a drag" would just totally rock.

\d
Comment 3 Dotan Cohen 2009-06-12 18:03:59 UTC 
> The window raising could happen only on mouse release and unless
> you initiated a drag inside the window.

"could" as in this is the solution that you propose?
Comment 4 Christoph Feck 2009-06-13 16:44:55 UTC 
Yep :)
Comment 5 Thomas Lübking 2009-08-11 21:16:50 UTC 

*** This bug has been marked as a duplicate of bug 195773 ***
Comment 6 Dotan Cohen 2011-12-04 18:17:55 UTC 

*** This bug has been marked as a duplicate of bug 36065 ***