On Wed, Jul 09, 2008 at 10:32:26PM +0200, Simon Thum wrote:
>> not sure if I get what you need to do but - the driver is expected to
>> set SetProperty, which is called when a client changes a device's
>> property.
> Ok, I'll try again: In order to support my acceleration code's tweaks
> (bug#8583), I'd like to attach some props to pointing devices. Of
> course, the driver doesn't know them and should not need to.
>> I'm in dix, so a possible solution would be to 'chain' SetProperty, i.e.
> unknown properties are passed to the previous handler (which was
> installed by me) by the driver, who kindly remembered what sat in the
> SetProperty slot just in case.
I replaced the single Set/GetProperty with a linked list. I'm sure the
WRAP/UNWRAP game provides hours of entertainment, but I personally hate it.
Aside from that, this forces drivers to go through an API rather than
accessing the DeviceIntRec struct directly, and in the long term this may just
be a good idea.
Cheers,
Peter