On Mon, Apr 30, 2012 at 10:54 PM, Peter Hutterer
> On Mon, Apr 30, 2012 at 10:10:59PM -0500, Favux ... wrote:
>> Another libwacom question for Waltop tablets. Could/should I create a
>> WCLASS_Waltop? Or should I follow the lead in wcmUSB.c in which case
>> the valid classes include Intuos4, Bamboo, and Graphire? Or should I
>> leave in the Waltop tablet data the class as WCLASS_UNKNOWN? Either
>> assign it unknown or leave class out altogether?
> Aren't the Waltops just largely identical to some of the wacom model lines?
I gather the wcmUSB.c assignments were based on the attempted linux
driver Waltop had. If true those correspondences were determined by
Waltop. I presume they based that on features, resolution, and maybe
pressure levels. I haven't really tried to determine correspondence
with features. The Waltop's can have things like pad buttons or hot
keys, scroll wheels, rings, and pucks but they apparently aren't
compatible with the Wacom equivalents which is why Nick is putting
them on the evdev driver.
The major difference I see between Waltop tablets is that the latest
Waltop models have battery-less styli and resolutions comparable to
the Intuos4. So there are at least two classes. Three if resolution
> If so, just pick the model line that is the closest. If not, it's better to
> create new classes for each Waltop line of models instead of one Waltop
I'll go with the wcmUSB.c until Nick decides differently. And by the
way there are a lot more Waltop PIDs in wcmUSB.c than those covered on
the DIGImend site. Right now there are seven data files which should
be it for while. That's mostly why I was thinking of one class.