index

How does Sawfish WM manage the keyboard(grab):

i'd like to make 2 tests: 1/ If you grab a key(+modifier) passively on a window, say "H-e", then want to write "i"

i wonder, if this is a desired behaviour (although i admit it is documented): i have a passive

-grab on H-i (H a modifier). Now when i set the auto-repeat delay to 2 seconds (just to be sure to do the right sequence) and do: Hyper, i, Hyper-up, e, i-up , e-up the grabbing client receivs the 'e' event. I wonder if that is useful. I think it could sometime happen by error.

therefore: i want to grab the Hyper_L

how to ungrab: get a window, and have it a grab_owner. Which has another passive grab, on the 'final' keys: say Enter.

I want to be able to stop key-event processing till the right window is focused. Also i don't want to write my password to another window, if the password-requesting window suddenly disapears.

(at the beginning) we have passive grab.

if we need more keys in the command-key-sequence we request active grab

why? try without

Quoting from Xgrab.html:

The interpretation of the remaining arguments is as for XGrabKeyboard. The active grab is terminated automatically when the logical state of the keyboard has the specified key released (independent of the logical state of the modifier keys).

XAllowEvents:

Ungrab keyboard:

My intervention:

i want two commands:

dont_allow_events

i.e. we want to wait for some event. This implies don't ungrab:

(set-dont-allow-events 1)

xallowevents_handling

don't ungrab:

Then i need to catch the right events:

-focus

-error

-> ungrab. ( no need to allow events)

Necessary re-adjustement:

grab-counter ... needs to be a defvar (in misc.jl)

Troubleshooting: