On Tue, Oct 12, 2010 at 9:55 PM, Jason alavaliant <[email protected]>wrote:
>
>> >
>> >
>> > 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).
>
Ah I see reading the git changelog you've purged TwinView from the source.
Seems a bit backwards that your advice in the entry is " (see commit
239822f9f4 "xsetwacom: add "MapToOutput" parameters.")" considering you've
said don't use xsetwacom :) It also leaves me a bit struck as I
understand it MapToOutput requires randr 1.2 and I'm stuck with the
proprietary<http://en.wikipedia.org/wiki/Software_license#Proprietary_software>nvidia
driver that doesn't support rand 1.2.
I guess I should be using the 'Coordinate Transformation Matrix' property
directly from my code? Only thing I'm unclear on there is there is a
way to toggle between multiple displays with this sort of setup? (you used
to be able to map a button to the DisplayToggle action but if you are only
mapping to one screen at a time it doesn't look to me like the input driver
would know about other displays?). Should I be coding my own shortcut
button to runsome code to alter the 'Coordinate Transformation Matrix'
property directly to do the toggling between displays or is there a function
I've missed?
Thanks
-J
------------------------------------------------------------------------------
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
