"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.
This commit is contained in:
parent
507782e5d4
commit
7d30d0007d
3 changed files with 4 additions and 0 deletions
|
@ -965,6 +965,7 @@ void Slit::buttonPressEvent(XButtonEvent &be) {
|
||||||
return;
|
return;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
XAllowEvents(dpy, SyncPointer, CurrentTime);
|
||||||
if (!myMenuWasVisible)
|
if (!myMenuWasVisible)
|
||||||
screen().placementStrategy().placeAndShowMenu(m_slitmenu, be.x_root, be.y_root, false);
|
screen().placementStrategy().placeAndShowMenu(m_slitmenu, be.x_root, be.y_root, false);
|
||||||
}
|
}
|
||||||
|
|
|
@ -550,6 +550,7 @@ void Toolbar::buttonPressEvent(XButtonEvent &be) {
|
||||||
return;
|
return;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
XAllowEvents(dpy, SyncPointer, CurrentTime);
|
||||||
screen()
|
screen()
|
||||||
.placementStrategy()
|
.placementStrategy()
|
||||||
.placeAndShowMenu(menu(), be.x_root, be.y_root, false);
|
.placeAndShowMenu(menu(), be.x_root, be.y_root, false);
|
||||||
|
|
|
@ -2439,6 +2439,8 @@ void FluxboxWindow::buttonPressEvent(XButtonEvent &be) {
|
||||||
// - refeed the event into the queue so the app or titlebar subwindow gets it
|
// - refeed the event into the queue so the app or titlebar subwindow gets it
|
||||||
if (be.subwindow)
|
if (be.subwindow)
|
||||||
XAllowEvents(display, ReplayPointer, CurrentTime);
|
XAllowEvents(display, ReplayPointer, CurrentTime);
|
||||||
|
else
|
||||||
|
XAllowEvents(display, SyncPointer, CurrentTime);
|
||||||
|
|
||||||
// if nothing was bound via keys-file then
|
// if nothing was bound via keys-file then
|
||||||
// - raise() if clickRaise is enabled
|
// - raise() if clickRaise is enabled
|
||||||
|
|
Loading…
Reference in a new issue