[PATCH] Input device properties

Simon Thum simon.thum at gmx.de
Wed Jul 9 02:51:05 PDT 2008

Hi Peter,

thanks a lot! Looks good to me, however one question: As I want to 
intercept updates to props in dix, am I expected to overwrite 
SetProperty? Can I rely on drivers not cancelling me (i.e. chaining as a 
part of the spec) or how would you say this could be done best?



Peter Hutterer wrote:
> This patch adds input device properties modelled after randr output
> properties (and by modelled I mean mostly copied).
> Why do we want them?
> Currently the method to talk to a driver is through the ChangeDeviceControl
> request, which basically routes binary data from the client to the driver and
> vice versa. Adding new control types requires a protocol bump.
> The properties are simply X atoms that can be set on the device, and allow for
> arbitrary options without having to update the server and/or the protocol.
> Long-term this would allow us to deprecate the ChangeDeviceControl request.
> Additional patches for libXi, app/xinput and xf86-input-evdev are available in
> http://people.freedesktop.org/~whot/patches/device-properties
> The evdev driver provides the ability to set middle button function + timeout
> through properties as a simple demo.
> Example usage for xinput:
> whot at emu:~$ xinput --list-props "USB Optical Mouse"
> Device 'USB Optical Mouse':
>         Middle Button Emulation:        2
>         Middle Button Timeout:          50
> whot at emu:~$ xinput --set-int-prop "USB Optical Mouse" "Middle Button Timeout" 16 500 
> Note that some of the patches require cleanup and no documentation has been
> written yet. Unless there's any NACKs, I'll push by the end of the week and
> try to get the specs updated.
> Cheers,
>   Peter
> ------------------------------------------------------------------------
> _______________________________________________
> xorg mailing list
> xorg at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/xorg

More information about the xorg mailing list