Press question mark to see available shortcut keys


Discover
Join Google+
Report an issue
Help
©2017 Google • Privacy Policy • Terms of Service • Maps Terms
Region


  • My Account
  • Search
  • Maps
  • YouTube
  • Play
  • Gmail
  • Drive
  • Calendar
  • Google+
  • Translate
  • Photos
More
  • Shopping
  • Docs
  • Books
  • Blogger
  • Contacts
  • Hangouts
  • Keep
Even more from Google
Sign in
Sign in
Peter Hutterer
Public
Sep 21, 2013

Draft of a wayland protocol to support Wacom tablets sent to list. Comments appreciated.

I do have some implementation, but it still lacks things like proximity events etc, so I won't claim that's ready for testing yet.

http://lists.freedesktop.org/archives/wayland-devel/2013-September/011173.html
[RFC DRAFT] graphics tablet protocol extension
[RFC DRAFT] graphics tablet protocol extension. Peter Hutterer peter.hutterer at who-t.net. Fri Sep 20 03:35:42 PDT 2013. Previous message: [PATCH wayland] protocol: validate the protocol against a dtd; Next message: [PATCH wayland] Export the Wayland protocol XML file; Messages sorted by: ...
lists.freedesktop.org
13 comments
13
6 plus ones
6
3 shares
3
Shared publicly•View activity
View 7 previous comments
  • Peter Hutterer's profile photo
    Peter Hutterer
    +Alexander Patrakov current idea is to only expose the touch parts as touch and the buttons as part of the stylus. That may need a switch in the compositor so you could reassign, with e.g.a bamboo being like a touchpad with buttons. That would be a compositor implementation issue though.
    Sep 21, 2013
  • Peter Hutterer's profile photo
    Peter Hutterer
    +Thiago Macieira of course. There s a fine line between easy and not enough though :)
    Sep 21, 2013
  • Stefan Brüns's profile photo
    Stefan Brüns
    One think I would really like is a "softbutton hover" event. The Aiptek tablets do this, there is a "macro key" area at the top of the normal tablet surface. As soon as you move the pen to the top edge it stops sending coordinates but key numbers plus the normal proximity/pressure/button bits.
    The windows driver shows a small tooltip when hovering over the macro keys, making hitting it without looking at the tablet really simple.
    Sep 28, 2013
  • Peter Hutterer's profile photo
    Peter Hutterer
    I did think about soft button events and the best (and only workable) solution I've come up with so far is to integrate that in the compositor.

    The compositor knows when the pointer is over there, so it would intercept the events and mangle them into whatever else is supposed to happen .
    Sep 28, 2013
  • Stefan Brüns's profile photo
    Stefan Brüns
    +Peter Hutterer For the Aiptek this wont work. The macro keys are not reported as events in the normal coordinate space, but as keys 1...N, although they are physically located at the top of the drawing area. The driver could fake coordinates, but what's the correct value for above top left, ie 0/0?
    Oct 4, 2013
  • Peter Hutterer's profile photo
    Peter Hutterer
    +Stefan Brüns if the kernel already reports keys, then we should just stick with that. Beyond that, I need to think about it. Would be great if you could send me an email with that info though, easier to search for in the future
    Oct 5, 2013
Add a comment...