"the least oversight", part #2 playing with the side borders I figured that clicking them (after ading them ;-) would freeze the pointer. In addition harden the menu-triggering paths for slit and toolbar. The menu will implicitly grba/release stuff, but in case it fails to show up .... better safe than sorry.
Thomas Lübking thomas.luebking@gmail.com
3 files changed,
4 insertions(+),
0 deletions(-)
M
src/Slit.cc
→
src/Slit.cc
@@ -965,6 +965,7 @@ XAllowEvents(dpy, ReplayPointer, CurrentTime);
return; } + XAllowEvents(dpy, SyncPointer, CurrentTime); if (!myMenuWasVisible) screen().placementStrategy().placeAndShowMenu(m_slitmenu, be.x_root, be.y_root, false); }
M
src/Toolbar.cc
→
src/Toolbar.cc
@@ -550,6 +550,7 @@ XAllowEvents(dpy, ReplayPointer, CurrentTime);
return; } + XAllowEvents(dpy, SyncPointer, CurrentTime); screen() .placementStrategy() .placeAndShowMenu(menu(), be.x_root, be.y_root, false);
M
src/Window.cc
→
src/Window.cc
@@ -2439,6 +2439,8 @@
// - refeed the event into the queue so the app or titlebar subwindow gets it if (be.subwindow) XAllowEvents(display, ReplayPointer, CurrentTime); + else + XAllowEvents(display, SyncPointer, CurrentTime); // if nothing was bound via keys-file then // - raise() if clickRaise is enabled