HIG (Future of KDE Development)

Benjamin Meyer ben at meyerhome.net
Fri Feb 18 11:36:19 GMT 2005


On Friday 18 February 2005 10:25 am, Matthias Ettrich wrote:
> On Friday 18 February 2005 12:56, Benjamin Meyer wrote:
> > Nope, no problem here.  It works like this:
> >
> > Assume you have two windows A and B, both from the same application. B is
> > in front of A hiding it partially. Now you want to bring A to the front.
> > You click on it. kwin raises _B_, then kwin raises A. Result: A is in
> > front.
>
> Yep, that's a common thing in window managers. KWin does it right for
> transient relationships, and it did so for ages. If an application has two
> non-modal dialogs that are transient for a main window, raising any of the
> dialog would raise the whole group (meaning all three windows), but the
> dialog _inside_ the group above the other dialog.

But that is not what this patch does.  KWin has always done what you are 
talking about for transient relationships.  This patch  raises *all* windows 
from the application to the top, (keeping their order) and puts the one you 
clicked on to the very top.  It may sounds odd, but after using it for a day 
I have patched every system I use.  It just works as I have always expected 
windows to work.

When editing images in gimp and I have 5 gimp windows open and 15 other 
application windows open.  I am done working on an e-mail and want to started 
editing my image again.  I click on a little patch of the image on the 
screen.  That gets raises, but so does all the pallet windows allowing me to 
use them without raising them all one by one from the taskbar (or god forbid 
using a whole nother desktop).  What finally spawned me to do this was the 
new Qt designer which has multiple windows just like Gimp.

It is kinda like every application has its own plane.  When you raise a window 
you raise the entire plane for that application.

> But instead of raising one widget after the other, you want to bring the
> topmost one to the front, and then stack the others below that one (to
> avoid horrible flicker).
>
> Matthias

Good idea.

-Benjamin Meyer 

-- 
aka icefox
Public Key: http://www.icefox.net/public_key.asc




More information about the kde-core-devel mailing list