[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: KWin locks KDE with Alt+Tab
From:       Daniel Molkentin <molkentin () kde ! org>
Date:       2001-06-18 19:08:46
[Download RAW message or body]

On Monday 18 June 2001 21:11, Ellis Whitehead wrote:

> On Monday 18 June 2001 19:27, Daniel Molkentin wrote:
> > If you use Alt+Tab to cycle though all windows, kwin gets
> > stuck in the window summary widgets and apperantly eats
> > all keyboard and mouse inputs.
>
> Can you describe exactly under what circumstances it happens?  I can't
> reproduce it over here...

Now that Matthias mentions: Indeed it happens especially under high load 
(i.e. while compiling) while At+Tab'bin around heavily....

>
> On Monday 18 June 2001 14:15, Matthias Ettrich wrote:
> > Yes, lately I've seen a timing issue there. I think this started when
> > somebody made the alt-tab handling configurable and started using
> > KGlobalAccel for it. I assume it's a race condition with some CurrentTime
>
> The problem that you're refering to occurs when Workspace doesn't get the
> key release event.  KGlobalAccel gets the original keypress event and does
> an "emit activated()", ultimately calling
> "Workspace::slotWalkThroughWindows()". But if a lot is going on, the
> release event occurs before the slot is activated, so Workspace never sees
> it.  The solution is to check
> the key state map once Workspace gets the event and see if the modifier key
> has already been released or not.
> I can't imagine what could have changed in this respect, though, unless
> Workspace itself used to XGrabKey (Alt+Tab)?
>
> Take care,
> Ellis
>

Thanks!

Greetings,

</daniel>

-- 
KDE 2.1 - Conquer your Desktop!
http://www.kde.org

[prev in list] [next in list] [prev in thread] [next in thread]