Dave Mielke <[EMAIL PROTECTED]> writes: > Can anyone tell me how Speakup intercepts key events?
Speakup intercepts all sorts of things by directly patching the kernel. > If we use this scheme how will we be interacting with it? I guess its a bit unpredictable if we are dealing with something that patches into the kernel. It depends on the patch how it interacts with input device clients from user space. > Does it intercept them first, do we, does one scheme disable or > conflict with the otehr, etc? If speakup intercepts on the hardware level (which I guess they do), I guess it will see they keypress anyway. I highly doubt speakup uses the input layer API, they dont like using APIs :-). But, given the current kernel API, this approach (input devices) is the right way to go for a user space application. If we want to intercept keypresses, we really want to do it this way. I'd go as far as claiming if this conflicts with some other patches, the patches are broken, not the input device approach. -- CYa, Mario _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
