Andreas Pakulat apaku at gmx.de
Sat Aug 7 11:13:15 BST 2010

On 07.08.10 12:03:00, Michael Leupold wrote:
> Hi there,
> Am Samstag, 7. August 2010, 11:54:40 schrieb Christoph Feck:
> > On Saturday 07 August 2010 11:44:12 Michael Leupold wrote:
> > > Revert r1156762. KApplication has to keep its event filtering code.
> > > Replacing it with the KSystemEventFilter methods unfortunately disrupts
> > > how KGlobalAccel works, including KWin messup.
> > 
> > Oh :( Since KWin could be fixed by a different patch (see bug 246545), I
> > would really like to get some more "why it broke" answers, because I think
> > the idea of the patch should not be silently discarded.
> > 
> > Are there any other regressions besides the Alt+Tab bug? Does KGlobalAccel
> > maybe have a different bug that only was showing now?
> > 
> > Christoph Feck (kdepepo)
> > 
> > References:
> > https://bugs.kde.org/show_bug.cgi?id=246545
> Unfortunately I didn't have too much time to look into it but we had a short 
> discussion about it on IRC (mgraesslin, mjansen and me).
> As I understand it the main problem is that KGlobalAccel snatches the shortcut 
> because it's registered as a global shortcut. However KWin needs to treat it 
> in a special way due to the tabbox staying open while alt is pressed. Now the 
> main problem in that specific case seems to be that the order in which the 
> various code pieces/applications get the events is reversed and thus KWin 
> doesn't receive the event (as I said mostly guessing, not too much debugging 
> due to lack of time).

As I said in my other mail kwin wasn't the only app being broken. The
logout dialog (in ksmserver as far as I understood) also suffered from
this, allowing no keyboard interaction anymore.


Your lucky number has been disconnected.

More information about the kde-core-devel mailing list