Review Request: Fix KSelectionWatcher / KWindowSystem::compositingChanged signal
Thomas Lübking
thomas.luebking at web.de
Fri Jan 4 22:21:23 GMT 2013
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/107983/
-----------------------------------------------------------
(Updated Jan. 4, 2013, 10:21 p.m.)
Review request for kdelibs, kwin, Plasma, Aaron J. Seigo, Marco Martin, Martin Gräßlin, and Luboš Luňák.
Changes
-------
Adding plasma.
kdelibs/plasma/theme.cpp connects the WindowSystem signal.
It might (for now?) be only me encountering bug #179042 but i suggest to have a short look at the testcase, test how suspending the compositor (shift+alt+f12) impacts the theme and report back.
Description
-------
It works fine here (tested so far KWindowSystem signal, KSelectionWatcher only with kwin) with kwin (shift+alt+f12), xcompmgr, compiz & "metacity -c" and e17.
Didn't try xfce nor mutter.
Technically:
I do not at all understand why KWindowSystem is *not* watching the root window - KSelectionOwner for one is sending events to the root and this also seems the case for all other WMs (at least everything now starts to cause the signal to be emitted)
The KSelectionWatcher failure seems to be kwin specific (wrote me a cleaner testcase), there'll be some X11 event processing on top that eats away the client messages.
So this one can be scratched from the patch, the KWindowSystem issue remains.
This addresses bug 179042.
http://bugs.kde.org/show_bug.cgi?id=179042
Diffs
-----
kdeui/windowmanagement/kwindowsystem_x11.cpp f9b3cc1
Diff: http://git.reviewboard.kde.org/r/107983/diff/
Testing
-------
see summary
Thanks,
Thomas Lübking
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20130104/e8d46b34/attachment.htm>
More information about the kde-core-devel
mailing list