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

List:       kwin
Subject:    [Bug 54885] mainwindow shouldn't be hover shaded when the focus moves
From:       Marcel Partap <mpartap () gmx ! net>
Date:       2007-04-22 15:54:58
Message-ID: 20070422155458.14657.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=54885         




------- Additional Comments From mpartap gmx net  2007-04-22 17:54 -------
...almost filed another duplicate, this problem is still there. It's kinda like an \
elephant trap, it don't bother you if you're a mouse but if you are an elephant it's \
constant terrror-- would be great if someone fixes this before christmas-- it seems \
to be related to this in events.cpp: void Client::leaveNotifyEvent( XCrossingEvent* e \
) [...]
        // TODO this still sucks if a window appears above this one - it should lose \
                the mouse
        // if this window is another client, but not if it's a popup ... maybe after \
KDE3.1 :(  // (repeat after me 'AARGHL!')
        if ( !lostMouse && e->detail != NotifyInferior ) 
            {
            int d1, d2, d3, d4;
            unsigned int d5;
            Window w, child;
            if( XQueryPointer( qt_xdisplay(), frameId(), &w, &child, &d1, &d2, &d3, \
&d4, &d5 ) == False  || child == None )
                lostMouse = true; // really lost the mouse
            }
I don't quite understand how this works and could not come up with code to fix it, \
fortunately there are those who can ;) \
_______________________________________________ Kwin mailing list
Kwin@kde.org
https://mail.kde.org/mailman/listinfo/kwin


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