diff options
| author | Victor Kareh <[email protected]> | 2017-08-14 06:31:10 -0400 |
|---|---|---|
| committer | Martin Wimpress <[email protected]> | 2017-08-14 11:31:10 +0100 |
| commit | 680dca33ba526ae0d2dc333ac26a1c5872d86120 (patch) | |
| tree | d03b3776818c3f2c5a6e26b01e36f11087575289 /doc | |
| parent | d051953c1412ced4a140f7f4253c823bbe358165 (diff) | |
| download | marco-680dca33ba526ae0d2dc333ac26a1c5872d86120.tar.bz2 marco-680dca33ba526ae0d2dc333ac26a1c5872d86120.tar.xz | |
Fix synthetic keybinding/button-grab window (#342)
* Determine focused window when processing synthetic events
When a client is passively grabbing keybindings that it does not need,
it sends them up for other clients to process.
Often in this situation, the event contains the wrong window (either
root, for global keybindings, or the original client itself). This means
that Marco will attempt to process the event for the wrong window.
This is not an issue for global keybindings within Marco, as the focused
window does not matter. However, for shortcuts that operate directly on
specific windows, the event gets lost.
This change addresses this by determining what the currently-focused
window is, regardless of which client forwarded the event.
* Determine window under pointer when processing synthetic events
When a client is passively grabbing mouse clicks that it does not need,
it sends them up for other clients to process.
Often in this situation, the event contains the wrong window (either
root, for global keybindings, or the original client itself). This means
that Marco will attempt to process the event for the wrong window.
This change addresses this by determining what the current window under
the mouse pointer is, regardless of which client forwarded the event.
* Remove unused development data
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions