Jason Gerecke <killertofu@...> writes:
> Thankfully, not too terribly long. I've got representatives of most of
> the tablets handy, though some with different button layouts (e.g.
> Intuos4 Small) were guesses.

I've updated 2 of the definitions you provided, which claimed to have both a 
builtin device and 
one that was reversible. That's not possible, for those devices the tablet 
rotation follows the 
screen rotation, so you'd just change the screen's rotation instead.

I've also noticed problems with the "Ring" value. At least the Cintiq 21UX2 has 
touch rings on 
each side of the device, but the definition says "Ring=false".

I've also noticed that those rings weren't explicitely mentioned in the 
schemas. Finally, those 
schemas have the button numbering wrong. For example, the Intuos4 6x9 that I 
have in front of 
me. In the definition, you have:
# Button Map:
# (A=1, B=2, C=3, ...)
#
#    *-----------------------*
#    |                       |
#  B |                       |
#  C |                       |
#  D |                       |
#  E |                       |
#  A |        TABLET         |
#  F |                       |
#  G |                       |
#  H |                       |
#  I |                       |
#    |                       |
#    *-----------------------*

When in reality it should be:
# Button Map:
# (A=1, B=2, C=3, ...)
#
#      *-----------------------*
#      |                       |
#   B  |                       |
#   C  |                       |
#   H  |                       |
#   I  |                       |
#  (A) |        TABLET         |
#   J  |                       |
#   K  |                       |
#   L  |                       |
#   M  |                       |
#      |                       |
#      *-----------------------*
# (A) is a touch ring, middle-click 1, 4/5 through the scroll wheel

Would it be possible for you to update the schematics to reflect that?

I will probably also change the Ring property to a number of rings, rather than 
a simple 
boolean.

> > I'll need to transform that data into something usable programmatically 
soon to
> > get the button mapping on its way.

This is going to get slightly complicated. 

In the definitions, we will need to:
- name all the buttons (that'll need to be translated)
- which mouse button they correspond to
- and possibly include some metadata for LED setting if necessary (which I have 
no idea what 
this should look like)

Does that sound appropriate?


------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Linuxwacom-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Reply via email to