On Mon, Aug 30, 2010 at 05:28:36PM -0700, Ping Cheng wrote: > On Sun, Aug 29, 2010 at 5:55 PM, Peter Hutterer > <[email protected]> wrote: > > On Sun, Aug 29, 2010 at 05:21:22PM -0700, Ping Cheng wrote: > >> On Friday, August 27, 2010, Peter Hutterer <[email protected]> > >> wrote: > >> > prop_screen is the one used for the screen area configuration. > >> > >> From what I remember _screen is a read and write prop that can set/get > >> the screen number that the driver is configured to. _screen_area is a > >> read-only prop that returns the actual screen coordinates that the > >> tablet is mapped to. > > > > the screen number is value 1 in prop_display. I think it may just be > > copy-paste leftover, the only references for prop_screen_area I have in my > > tree are: > > > > $> git log -Sprop_screen_area --pretty=oneline > > 0aa4ab4d62df6c325cc78eee830e8b800bca6a18 Remove unused prop_screen_area > > property. > > 3718c605520fd1d992e0fdedbdc1136581b808e5 Clean up more properties. > > We didn't implement the screen_area since you suggested that we don't > need it any more. linuxwacom still has that option(s) > (STopX/STopY/SBottomX/SBottomY). > > > it was introduced in 3718 but didn't do anything there and hasn't been > > touched since. > > Right now the screen_area is mainly used to report TwinView settings. > I guess it would be a question of if we want to support screen mapping > or not. If we do, screen_area would be needed unless user has other > means to get the screen area that the tablet is mapped to.
the "Coordinate Transformation Matrix" property available on all pointer devices (regardless of the driver) provides that option. that's what the xsetwacom MapToOutput applies to as well. It provides mostly arbitrary mapping to any screen region. > I heard you say that we should not support screen mapping in the > driver. So, it is unnecessary, I guess (I dare not to say no since if > I say no, you might say yes, somehow :). that's still my stance. input drivers should not deal with screen mappings as they have no idea of the screen mappings at any given time. unlike clients, they don't get notified of screen mappings and static screen mappings are getting more and more uncommon. Cheers, Peter ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
