multi-touch-dev team mailing list archive
-
multi-touch-dev team
-
Mailing list archive
-
Message #00761
Re: tablets and auto-rotation
Last June and July we had an excellent discussion about screen rotation
for tablet PCs. To the best of my knowledge, this continues to be an
issue in Ubuntu.
I'd like to share the resources and insights discussed last year with a
wider audience for two reasons:
1) this could be of benefit to others, and
2) it could spark a new discussion with better-imagined new solutions
to try
I will forward the other emails in the thread to this list, so please
forgive the coming email flood on auto-rotation!
Thanks,
d
-------- Original Message --------
Subject: Re: [Private-sparsha-dev] tablets and auto-rotation
Date: Mon, 28 Jun 2010 06:00:21 -0600
From: Duncan M. McGreggor <duncan.mcgreggor@xxxxxxxxxxxxx>
To: Rick Spencer <rick.spencer@xxxxxxxxxxxxx>, Bryce Harrington
<bryce@xxxxxxxxxxxxx>, Alberto Milone
<alberto.milone@xxxxxxxxxxxxx>, Neil J Patel
<neil.patel@xxxxxxxxxxxxx>, David Barth <david.barth@xxxxxxxxxxxxx>
On Jun 27, 2010, at 5:43 PM, Rafi Rubin wrote:
> On 06/27/10 18:28, Mohamed Ikbel Boulabiar wrote:
>> Just a little word about the ntrig driver and X,
>> I have a tablet-pc where Windows flip the screen when I fold the
>> laptop into tablet mode.
>> In Linux, when I tried to flip the screen with xrandr, the input
>> stay mirrored.
>> So when I touch the screen, I see the cursor in the other side.
>>
>> Should we think also about these problems now ?
>> The dependency between input/output ?
>>
>> ik.
>
> Yes its a known problem, and to some extent the solution is also
> well known.
>
> I wrote a rotation wrapper that adjusts the parameters for both
> wacom and evdev
> ntrig pointers along with xrandr:
>
> http://ofb.net/~rafi/xrotate.zsh
>
> Its really a matter of where to put it. The author of easystroke
> also wrote a
> tiny little daemon that monitors xrandr events and updates all wacom
> devices, in
> the worst case, we could cannibalize/extend that. But during the
> UDS (or some
> time around then), someone mentioned using gconf, or something else
> that's
> already part of the standard set of running stuff to handle this.
> Either way,
> we should get back to the desktop people and make sure they
> integrate the
> auto-adjustments (something which had slipped my mind).
>
> Rafi
Rick, Bryce, Alberto, Neil, or David -- do you guys have any insight
on this problem and any current plans to address it for Maverick?
If there are none, who is the best person to work with to get it
addressed?
Thanks,
d
Follow ups