Ticket #593 (assigned usability)

Opened 11 months ago

Last modified 8 months ago

Monoprice tablet sends events as cursor (probably NSUnknownPointingDevice)

Reported by: c55inator@… Owned by: jeremyhu@…
Priority: Important Milestone: 2.7.5
Component: xserver Version: 2.7.2 (xserver-1.12.2)
Keywords: monoprice uc logic tablet pressure sensitivity strokes not appearing Cc:

Description

I switched to a new Monoprice [UC-Logic] tablet recently. It works perfectly in non-Xquartz apps [Seashore and ArtRage as well as the system pen panel], but in programs running through Xquartz it cannot make strokes. It can click menus and UI, but any lines I try to make on the canvas [In both GIMP and MyPaint] do not appear. Changing both the pen and Xquartz virtual pointer to "disabled" mode allows the tablet to be used as a mouse, but no pressure sensitivity is recognized.

Furthermore, when testing input events [and the pen mode set to screen] the only events recognized on the Monoprice tablet are "Enter" and "Leave", no button presses or motion events. When set to disabled, motion and button presses are noticed, but pressure is still not recorded.

I can attach any screeshots/casts or provide more system information if necessary. I use Xquartz-based art programs daily so I am very interested in getting this fixed.

Tablet Model: http://sourceforge.net/apps/mediawiki/digimend/index.php?title=UC-Logic_Tablet_WP1062

Change History

comment:1 Changed 11 months ago by jeremyhu@…

  • Status changed from new to closed
  • Resolution set to invalid

It's not a matter of being supported by XQuartz or not. XQuartz just listens for NSEvents that contain the tablet data. You need to get it working with OS X. Once it's working with OS X, XQuartz will use it.

comment:2 Changed 11 months ago by jeremyhu@…

  • Status changed from closed to reopened
  • Resolution invalid deleted
  • Milestone set to 2.7.3

Ok, based on the x11-users email chain, it looks like this is a bug in the tablet's driver. Events are being sent as the cursor device which makes me think that the device is probably using NSUnknownPointingDevice as its pointingDeviceType when we get an NSTabletProximityEventSubtype. If that's the case, we can work around it by adding a defaults option to switch how NSUnknownPointingDevice is handled. It's currently treated as NSCursorPointingDevice, but we can give the user the option of using NSPenPointingDevice instead.

comment:3 Changed 11 months ago by jeremyhu@…

  • Priority changed from Nice to Have to Important

comment:4 Changed 11 months ago by jeremyhu@…

  • Status changed from reopened to new
  • Summary changed from Monoprice tablet is not recognized by Xquartz to Monoprice tablet sends events as cursor (probably NSUnknownPointingDevice)

comment:5 Changed 11 months ago by jeremyhu@…

  • Status changed from new to assigned

comment:6 Changed 9 months ago by jeremyhu@…

  • Milestone changed from 2.7.3 to 2.7.4

comment:7 Changed 9 months ago by jeremyhu@…

  • Milestone changed from 2.7.5 to 2.7.4

comment:8 Changed 8 months ago by jeremyhu@…

  • Milestone changed from 2.7.4 to 2.7.5

I need to get 2.7.4 out to address a critical issue seen in OS X 10.8.2 and 10.7.5, so deferring everything that is not a regression.

Note: See TracTickets for help on using tickets.