search for: findtoplevelwindowatdisplay

...oneself back in the history of changes, right? Earlier this morning the version I pulled was just fine. This is the lastest commit stated in git log: --- commit 115082f76a549efb08b87f4f03d7fc27c53048f1 Author: David Reveman <davidr@novell.com> Date: Tue Mar 6 20:35:07 2007 +0100 Use findTopLevelWindowAtDisplay when receiving FocusIn events as the frame might be the window that got focused when the client window is shaded. --- Anybody with an idea what might be messed up atm? Best regards... MacSlow -- email - macslow@bangang.de www - http://macslow.thepimp.net lowfat - http://macslow.thepimp...

With raise_on_click disabled, I wanted to be able to raise a window with a button click sometimes. It seemed logical to do something like the lower window key binding. So I did it. It was quite simple, but here is the patch anyway. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/octet-stream Size: 3680 bytes Desc: not available

...Remove whitespaces. Require x11-xcb. Add XCB connection handle to CompDisplay. Add CompNoMask to REAL_MOD_MASK. Select for focus change events on frame windows. Revert "Select for focus change events on frame windows." Usage of lastFoundWindow in findTopLevelWindowAtDisplay is Avoid using lastFoundWindow in findWindowAtDisplay. Reduce code by using findWindowAtScreen in This should be taken care of by unhookWindowFromScreen. Include proper compiler flags and link libdecoration to Avoid use of strcasestr and case insensitive matching of...

...ormedScreen. Cleanup paintTransformedScreen a bit. Add comment about occlusion detection. Remove PAINT_WINDOW_CLIP_OPAQUE_MASK and Add getAllowedActionsForWindow function that plugins can wrap to Fix typo. Windows can't occlude anything when shaded. Use findTopLevelWindowAtDisplay when receiving FocusIn events Shut up compiler. Don't calculate available actions until plugins have initialized count should be incremented for each window. Add activeViewportX and activeViewportX members to the The active viewport coordinate solution is not good...