Xinput patches

[Peter Hutterer]

On Mon, Apr 13, 2009 at 05:53:18PM +0200, Simon Thum wrote:
> Peter Hutterer wrote:
>>>> - I'd prefer a commandline-switch --by-type to trigger this, rather than
>>>>   guessing from the name of the device.
>>> Yeah, that's more extensible and more work - likely I'd have to 
>>> revamp  parsing. This change doesn't block that path, so this can be 
>>> done when  ambiguous cases show up.
>>
>> no, this change should be done before we let the new notation in. otherwise it
>> just gets too confusing. also, historically, commandline switches are to
>> specify further options, not "magic" parsing of user-given parameters.
>>
>> Sorry, but I'll leave the patch out for now until we have the --by-type
>> support.
> Problem is: some invokations (setcp, list-props) are in a loop. I didn't  
> check why exactly this is so, but if it's an important use case then it  
> becomes awkward to mix notations that way.

list-props supports multiple devices, so you can say xinput --list-props 2 3 4
and it lists the properties of all four devices. Same with the others, AFAICT.
So that's easy to cope with, if --by-type is the first flag, then the rest are
type arguments, not deviceidis.

Cheers,
  Peter