Commented out the feature (you didn't think I would reimplement it, did you ?) :)
And took the opportunity of touching Makefile.am for including *.moc in *.cpp
(faster compilation, smaller link lines, less files...)
svn path=/trunk/kdebase/kwin/; revision=52667
This prevents a lot of stupid focus changes when you move a window
around with focusFollowsMouse.
(mouse moves -> focus changes -> window moves -> focus changes back)
svn path=/trunk/kdebase/kwin/; revision=51574
with kicker. This allows us to apply kicker rules for internalapplets
that are external to Kicker (e.g., kasbar and ktaskbar)
Also converted qDebug calls to kdDebug while I was debugging
svn path=/trunk/kdebase/kwin/; revision=50597
pasted everything from kwm. It works.
However, I don't know if this fits the new design or not. Maybe some
of the functions are accomplished elsewhere? I think Matthias needs
to take a look at this...
But like I said, it does work :-)
svn path=/trunk/kdebase/kwin/; revision=49849
if true (default), the lowered client looses focus, and the top of
stacking order gets it. Something is not working if one lowers many
windows one after another... investigating
svn path=/trunk/kdebase/kwin/; revision=48229
Note that it leaves the focus where it was, which may seem strange if the
to be lowered window becomes fully obscured, but to change focus would be
the purpose of the calling function. To be discussed.
svn path=/trunk/kdebase/kwin/; revision=48202
to be avoided. It also updates nicely. Just move kicker from the
bottom to the left, say, and open a new window. It doesn't cover
kicker. Maximise. Still doesn't cover. Seems to work, then.
svn path=/trunk/kdebase/kwin/; revision=47602
which otherwise would occur when you click on the Alt-Tab-window with the
mouse. I hope I didn't break anything because this X-stuff is rather mystical.
BTW Why does KWin get so many "MotionNotify" events when you move your mouse
across certain windows?
svn path=/trunk/kdebase/kwin/; revision=47554
which want to be permanently visible.
I've used an XAtom called '_NET_AVOID_SPEC'. This of course can change
if need be. I think it's correct according to the wm spec, but the
wm spec seems to be empty on gnome.org, so who knows.
Windows can choose to be avoided by setting an XTextProperty
with one value, which can be either 'N', 'S', 'E', or 'W', according
to which screen edge they are anchored to.
kwin then sets its 'clientArea' rect appropriately, so that (in
theory at least) clients will not enter this area in some circumstances,
such as when being mapped for the first time.
You can see that this actually works if you start lots of konsoles. They
don't appear over the panel. I don't know what happens if you move the
panel, but I presume things will be screwed up, because I haven't
looked at that yet.
If you maximise a window, it'll still fill the screen, because the
implementation of maximise in kwin/client.cpp doesn't take account
of the workspace's clientArea rect. This is easy to fix, but I've
been awake for too long, so I'll do it after 42 winks.
svn path=/trunk/kdebase/kwin/; revision=46772
and it kept segfaulting because I wasn't releasing windows, and b) The plugins
didn't want to resolve anything in the kwin executable, only to the other
libs. I finally solved this by using -rdynamic in kwin's LDFLAGS, which I hope
is okay ;-)
svn path=/trunk/kdebase/kwin/; revision=37234
before... doesn't it make sense that [menu] would work for the
MENUBARS? Yeesh... I'm not sure what I was drinking that day.
Anyway, I think I got it now. Toolbars use [tools] (how about that!) :-)
svn path=/trunk/kdebase/kwin/; revision=37041
