role of addon-input?

[Matthew Garrett]

On Sat, Mar 28, 2009 at 09:16:54AM -0400, pgf at laptop.org wrote:

> addon-input has support for generating dbus "ButtonPressed"
> events for a long built-in list of "special" (mostly multimedia)
> keyboard buttons.  but if those buttons are generated by an input
> device which is eventually handled by an X server, then they'll
> never be seen, since the X server (its evdev driver?) uses
> EVIOCGRAB on its input devices, effectively preventing anyone
> else from eavesdropping on the device.  in other words, for many
> of the input devices addon-input monitors, addon-input will never
> receive any input events to handle.

evdev will only do EVIOCGRAB if you pass the GrabDevice argument. Since 
it breaks things, it's recommended that you not do that.

-- 
Matthew Garrett | mjg59 at srcf.ucam.org