>> /*
quoted text >> + * Device properties and quirks
>> + */
>> +
>> +#define INPUT_PROP_POINTER 0x00 /* needs a pointer */
>> +#define INPUT_PROP_DIRECT 0x01 /* direct object manipulation */
>
> fwiw, I think the common term for these is "direct input devices", at least
> that's how a lot of the research literature refers to them. Might be good to
> use the same term.
Changed, thanks.
quoted text > either way, not sure about this one. I've worked with devices that were
> indirect by nature but used directly. e.g. the magic touchpad could quite
> easily be used as direct input device with an top-down projector. the
> decision to use it as an indirect device is a UI decision.
> Likewise, some mountable direct-touch touchscreens can be used indirectly if
> the touchscreen isn't mounted straight on the display. This is very much a
> setup-specific property and I'm not sure about the value of this
> information.
As Dmitry stated already, this is foremost for automatic setup. The idea to
elevate these properties to the main configuration source is also interesting.
Thanks,
Henrik
--
unsubscribe notice To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
majordomo@vger.kernel.org
More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
http://www.tux.org/lkml/
Messages in current thread:
Re: [RFC v2] input: Introduce device information ioctl , Henrik Rydberg , (Thu Dec 16, 7:18 am)