Quoting "Felix E. Klee" <[EMAIL PROTECTED]>: > We're trying to realize the following functionality with a Wacom > Graphire tablet: > > On the tablet the user has a sheet of paper with buttons printed on > it. When he clicks on a button, then a script should be started. > > Ideally, there's also an area on the tablet that can be used for scribbling, > e.g. after starting an appliction such as the Gimp by clicking on a > certain tablet button (= button drawn on the paper). However, this > functionality is not too important at the moment, and I guess it can > be realized by defining two active areas on the pad. > > So, how do we realize the buttons? At the moment, I see several > solutions: > > A Map the tablet to the user's display. On the display, an application is > open that shows buttons corresponding to those on the tablet. > > Without surprise, this is not what we want. The user should be able > to work with another application in parallel to using the tablet. > > B Use the same solution as A, but do everything in a second X-server whose > display is not shown on the user's monitor. > > C Display a very small window on the users display and map the area > where the window is shown to the tablet. This solution should work > AFAIK. However, the small window on screen may annoy the user. Also, > there's the problem that the application probably needs focus in order > to receive click events. > > D Use the same solution as C but display the window off screen. > > Is there another possible solution that we should be aware of? Which of > the above solutions are feasible?
As far as I know the driver can't translate a stylus press in a specific area into a button press at the moment. Nor can you translate a specifica area of the tablet onto only a part of the screen. So I'd say that you should indeed use A or C (with the window at a specific position) at the moment. Correct me if I'm wrong. However, these things are something I've discussed with Ping some time ago (see devel-ml archives, [1] and [2]), and there's also a feature-request about this [3] (as I interpret it at least). I've made a patch-series of one of the features in that discussion (nothing that would help you with your requests though) and most of it has been included in the latest dev-release. So things are happening. :) BR Magnus V [1]http://sourceforge.net/mailarchive/forum.php?thread_id=30958964&forum_id=19621 [2]http://sourceforge.net/mailarchive/forum.php?thread_id=31097788&forum_id=19621 [3]http://sourceforge.net/tracker/index.php?func=detail&aid=676326&group_id=69596&atid=525127 ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Linuxwacom-discuss mailing list Linuxwacom-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss