multi-touch-dev team mailing list archive
-
multi-touch-dev team
-
Mailing list archive
-
Message #00014
Re: updates, and my priorities
-
To:
Rafi Rubin <rafi@xxxxxxxxxxxxxx>
-
From:
Alberto Milone <alberto.milone@xxxxxxxxxxxxx>
-
Date:
Mon, 15 Mar 2010 12:22:52 +0100
-
Cc:
Rick Spencer <rick.spencer@xxxxxxxxxxxxx>, Scott James Remnant <scott@xxxxxxxxxxxxx>, Christian Robottom Reis <kiko@xxxxxxxxxxxxx>, Pete Graner <pete.graner@xxxxxxxxxxxxx>, Multi-touch Dev <multi-touch-dev@xxxxxxxxxxxxxxxxxxx>, Bill Filler <bill.filler@xxxxxxxxxxxxx>, Marjo Mercado <marjo.mercado@xxxxxxxxxxxxx>, Hugh Blemings <hugh@xxxxxxxxxxxxx>, Patrick McGowan <pat.mcgowan@xxxxxxxxxxxxx>, Andy Whitcroft <andy.whitcroft@xxxxxxxxxxxxx>
-
In-reply-to:
<4B9DFCC4.5060105@seas.upenn.edu>
-
Sender:
albertomilone@xxxxxxxxx
On 15 March 2010 10:24, Rafi Rubin <rafi@xxxxxxxxxxxxxx> wrote:
>
> The range/scaling parameters are not translating correctly. So there's
> still just a tiny bit to fix there.
>
Right, I recall facing that problem on Brian Murray's tablet pc (as I
don't own one) at the sprint in Portland.
> Good to know gnome-settings-daemon supports the wacom rotation. Though that
> doesn't seem to be working for me atm. Do I need to enable anything?
>
I guess this code that Federico Mena Quintero wrote never made it upstream:
http://gitorious.org/gnome-settings-daemon/gnome-settings-daemon/commits/randr-rotate-wacom-tablet
It relies on the xsetwacom command line tool to rotate wacom devices
and it would be relatively easy to do something similar for evdev
(preferably using Xlib and Xinput instead of a command line tool).
Having the input devices rotated when the screen is rotated is
definitely something which would be nice to have, I'm not sure about
what priority this has, maybe it's something that I could implement
after Lucid is released?
>
> I'm not volunteering to add the daemon support, I am completely unfamiliar
> with it. Actually usually I don't even use it, just fvwm....
>
The problem is that the daemon is specific to the desktop environment
that you use. This means that while it makes sense to have this code
in gnome-settings-daemon if you're using Gnome, (at least in theory)
the same thing will have to be rewritten for whatever DE/toolkit our
future OEM projects will use. I would like to see a smaller DE
agnostic daemon for this kind of things so that we can reuse it in
each project (to be honest, I was working on something similar but I
haven't had the time to complete it), but I'm digressing now.
Regards,
--
Alberto Milone
Sustaining Engineer (system)
Foundations Team
Canonical OEM Services
Follow ups
References