http://bugs.winehq.org/show_bug.cgi?id=12005
--- Comment #11 from John Klehm xixsimplicityxix@gmail.com 2008-04-17 10:15:34 --- Created an attachment (id=12266) --> (http://bugs.winehq.org/attachment.cgi?id=12266) Allow wizardpen to be detected as a stylus
Ahh sorry Dan I failed to read the entries before your patch posting #5.
The code that guards axes detection is this:
if (!axis_read_complete && Val->num_axes >= 5 && cursor->TYPE == CSR_TYPE_PEN)
My previous patch allowing devices with any number of axes makes it this: (KeithB you should see more progress in detection with just this patch)
if (!axis_read_complete && cursor->TYPE == CSR_TYPE_PEN)
axis_read_complete is only set to true inside that if block so we can conclude that cursor-TYPE isn't being set for wizardpens.
And of course it wasn't. we see in this block that either our device's name or type has to come up with a match in is_stylus:
cursor->PHYSID = target->id; cursor->NPBUTTON = 1; cursor->NPBTNMARKS[0] = 0 ; cursor->NPBTNMARKS[1] = 1 ; cursor->CAPABILITIES = CRC_MULTIMODE; if (is_stylus(target->name, device_type)) cursor->TYPE = CSR_TYPE_PEN; if (is_eraser(target->name, device_type)) cursor->TYPE = CSR_TYPE_ERASER;
And having wizardpen match in the is_stylus function is what this patch does. So with allow any num axes patch and this patch, the detection should get further.
If things still don't work with wizardpens then but the device detection DOES get further then a new wintab32 log would be good.
If device detection DOESNOT get any further with both these patches then I give up for now. =P