Keith == Keith Packard kei...@keithp.com writes:
Old thread, but I unfortunately couldn't work on it before now - The
issue is about binding touchscreen events to a randr output
Original thread is here:
http://thread.gmane.org/gmane.comp.freedesktop.xorg/40071
Keith It would need to be tied
On Thu, 08 Apr 2010 17:22:56 +0200, Peter Korsgaard jac...@sunsite.dk wrote:
- Add an XInput property to evdev to assign a screen number / randr
output name to a device
Use a window ID to identify the screen; the protocol never uses screen
'numbers'.
- Add an API to forward this info to
2009/8/6 David De La Harpe Golden david.delaharpe.gol...@gmail.com:
2009/8/3 Peter Korsgaard jac...@sunsite.dk:
Now, with xrandr instead of Xinerama there is only one screen and the
above doesn't work (the coordinates gets scaled to the entire screen
instead of the individual outputs).
What
Peter == Peter Hutterer peter.hutte...@who-t.net writes:
Hi,
Peter I don't think either is a particularly large undertaking, so
Peter it's worth tackling if you have the hardware and the test setups
Peter to actually do it.
Thanks - I do. I'm going on holidays from Tuesday on, but I'm back
Hi,
On Thu, Dec 17, 2009 at 10:35:16PM -0800, Keith Packard wrote:
I'd say tablets and touch screens should report raw device coordinates
and let the X server transform them as appropriate. It'd be really cool
if we could make all absolute devices report position in floating point
using a
Peter Hutterer wrote:
- randr notification. with screens being added and removed, there's no
driver interface that I know of that input drivers can use to get notified
about this stuff.
A hack I used years ago (well before RandR 1.2 and XI2 - I haven't checked
in a long time if it still
late reply, but better than never I suppose...
On Mon, Aug 03, 2009 at 03:23:39PM +0200, Peter Korsgaard wrote:
How are touchscreens in multiscreen setups supposed to work nowadays?
The issue with touchscreens is that their input events have to be
transformed according to configuration
On Fri, 18 Dec 2009 15:04:48 +1000, Peter Hutterer peter.hutte...@who-t.net
wrote:
there's two parts to it:
- xf86InputSetScreen seems broken, this should be fixed in the server.
though it's probably optimised for the Xinerama scenario, I think it
should be possible to set it up for
On Thu, Dec 17, 2009 at 09:27:07PM -0800, Keith Packard wrote:
On Fri, 18 Dec 2009 15:04:48 +1000, Peter Hutterer peter.hutte...@who-t.net
wrote:
there's two parts to it:
- xf86InputSetScreen seems broken, this should be fixed in the server.
though it's probably optimised for the
On Fri, 18 Dec 2009 15:41:00 +1000, Peter Hutterer peter.hutte...@who-t.net
wrote:
by default, devices cross screen boundaries and tablets/touchscreens map to
the range of the screen. With xf86InputSetScreen a driver could be mapped
to a single screen only, thus a right-hand corner would
Hi,
On Thu, Dec 17, 2009 at 10:35:16PM -0800, Keith Packard wrote:
From what I can see, there's no way of fixing the coordinate space issue
with any driver that uses xf86XInputSetScreen today as they all convert
From device to screen coordinates internally, before posting those
events to the
On Thu, Dec 17, 2009 at 09:27:07PM -0800, Keith Packard wrote:
On Fri, 18 Dec 2009 15:04:48 +1000, Peter Hutterer peter.hutte...@who-t.net
wrote:
there's two parts to it:
- xf86InputSetScreen seems broken, this should be fixed in the server.
though it's probably optimised for the
Keith == Keith Packard kei...@keithp.com writes:
Hi,
Keith I'd say tablets and touch screens should report raw device coordinates
Keith and let the X server transform them as appropriate. It'd be really cool
Keith if we could make all absolute devices report position in floating point
Keith
2009/8/3 Peter Korsgaard jac...@sunsite.dk:
Now, with xrandr instead of Xinerama there is only one screen and the
above doesn't work (the coordinates gets scaled to the entire screen
instead of the individual outputs).
What is the suggested solution for this? Add randr output tracking to
14 matches
Mail list logo
