On Sun, Jan 03, 2010 at 08:24:41PM -0800, Ping wrote: > >> One user case that I can think of is to map the whole tablet to a > >> window or a particular screen area to fully use the accuracy of the > >> tablet. That is why I added this "Feature Request > >> https://sourceforge.net/tracker/?func=detail&aid=1559640&group_id=69596&atid=525127"; > >> and assigned it to myself more than 3 years ago. However, this > >> feature has never been requested by anyone else so I've never got the > >> opportunity to prioritize it over other "urgent" support. > > > > I still don't know a real-world use-case for this tough. If you need the > > tablet mapped to a specific area on the screen, you'd likely want to do > > something on the screen. Which means interact with a specific application.. > > Yes, you are on the right track. The tablet to specific screen area > (or window in some people's term) mapping is aimed mostly at > applications and specific users. > > Take application for example. If we don't have the tablet to window > mapping (that's what it is now), applications can only use part of > the tablet that is mapped into a window if the whole tablet is mapped > to a screen or the whole desktop. In CAD and a few other graphic > design fields, the accuracy of their picture is so important that they > can not afford to waste the precious tablet active areas. > > The reason, I guess, that this feature has never been requested so far > is due to the fact that most "serious" graphic designers are using the > whole desktop or a particular screen (if they have multi-monitor > setup) with their apps. So, the current tablet to screen mapping is > good enough for them.
How many users have we had requesting this feature - and not just for playing around but because there's a real need for it? Mapping the tablet to a portion of the screen cannot be solved with a device grab and in-application coordinate mapping only if you need to use two applications at the same time within that portion of the screen. Ok, so you need to use two apps in a certain part of the screen - say exactly the centre. At this point you need an interface to modify the screen area at runtime since one of the applications may need to move or resize and you need to rescale that area with it. Once that need is there, it gets nasty, because you'll want to update that automatically, which means you'll have to have a tracking application that ideally communicates with the window manager to take care of this. All that with a driver-specific API. I'm still not convinced. > > And in that case, it's better to have the application deal with it than have > > some quirk in the driver that maps against arbitrary areas on the screen. > > It's not a quirk. It is a feature :). Given enough time, any unmaintained feature becomes a bug. Cheers, Peter ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
