Re: [DIGImend-users] Genius MousePen i608X Gimp 2.8RC1 issue

[Favux ... <fav...@gm...>]

On Wed, Apr 18, 2012 at 3:54 PM, Nikolai Kondrashov <sp...@gm...> wrote:
>
>> This was suppose to be solved by negative matches being
>> allowed in X Server 1.11, which should allow matching to the parent
>> device/stylus.  Don't know if it was, because I haven't investigated
>> this yet.  A quick look at 'man xorg.conf.d' doesn't seem to indicate
>> negative matching has been added in X Server 1.11.3.
>
>
> How is this matching supposed to work?

No idea.  That's all Peter said, that negative matching would be
available and that would fix it.  My guess has been that a new match
or option parameter would be introduced, called say DoNotMatch.  So
then with a Wacom graphics tablet with stylus, eraser, cursor, and pad
the stylus snippet would look something like:
        MatchDriver "wacom"
        DoNotMatch "eraser|cursor|pad"

>> This was a problem for the WizardPen driver also.  It could not handle
>> either a mouse or two devices and if the kernel said a mouse was
>> allegedly present the stylus didn't work.
>
>
> Sorry, I'm not sure I understand this.

Sorry, I didn't ever investigate it.  I assumed the WizardPen driver
didn't have code to support a mouse.  So maybe a Relative/Absolute
Mode conflict?  We did try to place the mouse on evdev while keeping
the stylus on WizardPen and that didn't work.  Not helped when both
devices had the same name.

>
>> So from my perspective this may be a feature missing from evdev.  But
>> not an evdev bug per se.
>
>
> I think I should look into the kernel code and see if I could assign names
> to input devices created from report IDs. Maybe I could assign the suffixes
> to them there.

That might be the cleanest solution if it is doable.

Favux