Re: [Linuxwacom-devel] [RFC PATCH] Duplicate the InputAttributes for dependent devices.

[Ping C. <pin...@gm...>]

The voting window is closed.  The official result is 3.5 to 1.5 (the
.5 is from Ron :).  Approach 1 gets approved (Signed-off-by:  Ping
Cheng)

Peter, go ahead and take your gang (of three and half :) with you to
get the job done!

I know I don't have friends here :(.

Ping

On Mon, May 24, 2010 at 6:13 AM, Chris Bagwell <ch...@cn...> wrote:
>
>
> On Mon, May 24, 2010 at 4:00 AM, Peter Hutterer <pet...@wh...>
> wrote:
>>
>> On Mon, May 24, 2010 at 11:27:23AM +0300, Alexia Death wrote:
>> > On Mon, May 24, 2010 at 10:30 AM, Peter Hutterer
>> > <pet...@wh...> wrote:
>> > > fwiw, there's no requirement for uniqueness in device names. It's
>> > > quite
>> > > common to have devices with the same name, many mouse/keyboard combos
>> > > have
>> > > two or more devices with the same name and so do many touchscreens.
>> > This is interesting. So If I use xsetwacom with a shared name, who
>> > gets the config?
>>
>> no-one, xsetwacom will complain and require that you specify the ID
>> instead
>> :)
>>
>
> No strong opinions on my side either but my concerns are on how it effects
> output of "xinput list".  Do I continue to see in that list what an "eraser"
> is vs. a "touch"? Or would I need to issue a secondary command to see its
> tags?
>
> I've come to terms with duplicate device names (i.e. 2 erasers) since its
> not unique to wacom.  So thats no biggy but it has been nice to immediately
> see which part of tablet in its xinput name.
>
> Also, thinking from a possible future configuration GUI perspective, it
> would be nice if we could somehow bind a subset of devices together (a
> unique value; maybe the xinput # of first device in chain; shared in a tag
> or something).  That way you know what wacom "common" options are shared
> among what other input devices.  This is especially useful for tablets that
> have 2 input devices (such as Bamboo's) and so two sets of common options.
>
> Chris
>