On Tue, Oct 12, 2010 at 09:55:32PM +1300, Jason alavaliant wrote: > On Tue, Oct 5, 2010 at 1:44 PM, Peter Hutterer > <[email protected]>wrote: [...] > > > > Haven't checked out the code because right now I'm at an airport and I'm > > not > > even sure when I can send this email. > > > > Please don't use xsetwacom. We have properties, they are the driver's > > official API. xsetwacom makes no guarantee for consistency or backwards > > compatibility on its commandline interface. It's intended for testing of > > settings at runtime, but not as a base layer for any other client. > > > > > I was wondering if that was the direction I should be going in. The main > reason I'm using xsetwacom currently is that wacom-config -v1 was originally > written as a wacomcpl compatible tool that let you change settings from > either tool (and there was no way to set things besides xsetwacom at the > time). Is there any guide that covers all the properties for the wacom > driver? I think I can reverse engineer what most settings are via > xsetwacom commands and watching how the properties change but things like > 'Wacom Display Options (263): -1, 0, 0' would be a lot faster to > understand with some notes. (I think the middle value is twinview based on > seeing it change when setting twinview via xsetwacom but I've got no idea > what the other two are.)
All the properties are documented in the wacom-properties.h file but not overly expressive. I haven't added the man pages yet because some of the properties are still in flux (e.g. the removal of TwinView related ones). so once wacom 1.0 comes out, the list of properties may not necessarily be the same. > > > 1) The biggest one that's causing problems for me currently is that in > > > 0.10.8/git the value for TPCButton seems to be backwards ( > > > > > https://sourceforge.net/tracker/?func=detail&aid=3075826&group_id=69596&atid=525124 > > ) > > > Since my code has TPCButton off by default as soon as anybody enters > > > wacom-config and saves their settings they end up with TPCButton acting > > as > > > if it's on due to the current off=on status. > > > > see the other email, but genererally if the setting for TPCbutton now works > > reverse to what it used to, it's a bug. > > > > > I can change my code to reverse the values I have assigned to TPCButton > > but > > > that will cause trouble for me if the reversed values get fixed in a > > later > > > linuxwacom release since then things will be backwards in ever-bodies > > > settings again (and by that point most people at the company I work at > > will > > > be using wacom-config v2 causing mass confusion). So I'd love > > > clarification on if the reversed on/off values for TPCButton are here to > > > stay or are something that will be fixed just as soon as somebody writes > > a > > > patch? > > > > > > > > > 2) TVResolution - This one I know is in a bit of a state of flux with > > > TVResolution being broken in 0.10.8 and only starting to be fixed in git > > > since the 0.10.8 release. I've been following the git changes and > > testing > > > and trying to get a working build it's looking much much better but > > there > > > still seems to be a few issues that are making it hard to support > > properly > > > from wacom-config ( > > > > > https://sourceforge.net/tracker/?func=detail&aid=3075831&group_id=69596&atid=525124 > > > limits you to limited functionality on one monitor). Then what is also > > > confusing me (but I've not logged a tracker item for it yet) is that if > > I > > > just set TwinView and TVResolution I can move from one twinview monitor > > to > > > the other by touching the edge of the screen as per usual. But if any > > > setting is used that effects tablet or screen mapping, ( say setting > > TopX > > > even if I set it to the current value it already has ) that stops the > > cursor > > > from moving between the screens, it stays locked to the left screen and > > > disconnecting and reconnecting the tablet seems to be the only way to get > > > out of that state that I've found. > > > > > > I'm unsure if I'm being premature logging bugs about the git TVResolution > > > support since it's still not part of on official release (and there might > > be > > > a developer who has their own big list of TwinView stuff they are still > > > working on?) or if this stuff is only being fixed as people point things > > > out/offer patches? > > > > my plan is to remove all multimonitor handling from the driver. this needs > > to > > be handled in the server, not in an input driver. > > > > hmm I guess that's more a long term plan? (as in that's not going to happen > in the next month). Nope, happened this month, will be in 0.10.9 :) commit 2a4447f9d84beac78bc256d436b93a5f8fcc55a7 Author: Peter Hutterer <[email protected]> Date: Fri Aug 27 15:33:02 2010 +1000 Purge TwinView driver support. Cheers, Peter ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
