On Jan 9, 2014 11:30 AM, "Michal Jaegermann" <michal@xxxxxxxxxxxx> wrote:
>
> On Thu, Jan 09, 2014 at 10:37:43AM -0700, Pete Travis wrote:
> > On Jan 8, 2014 7:03 PM, "Michal Jaegermann" <michal@xxxxxxxxxxxx> wrote:
> > >
> > > Maybe somebody knows a reasonable method of convincing a mouse that a
> > > screen has different dimensions than defaults?
> > >
> > Does `xinput` list a translation matrix property for your device ? I use
> > this for a touchscreen secondary display, your situation sounds vaguely
> > similar.
>
> xinput in this particular case reports the following:
>
> ⎡ Virtual core pointer id=2 [master pointer (3)]
> ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
> ⎜ ↳ USB OPTICAL MOUSE id=10 [slave pointer (2)]
> ⎜ ↳ ETPS/2 Elantech Touchpad id=13 [slave pointer (2)]
> ⎣ Virtual core keyboard id=3 [master keyboard (2)]
> ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
> ↳ Power Button id=6 [slave keyboard (3)]
> ↳ Video Bus id=7 [slave keyboard (3)]
> ↳ Power Button id=8 [slave keyboard (3)]
> ↳ Sleep Button id=9 [slave keyboard (3)]
> ↳ Asus EeePC extra buttons id=11 [slave keyboard (3)]
> ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]
>
> xrandr will rescale a screen output but this is only mildly useful due to
> https://bugs.freedesktop.org/show_bug.cgi?id=39949 as mentioned by Felix.
>
> Michal
> --
Your next step would then be something like `xinput list-props 10` or so. I'm not in a position to write a tutorial at the moment, some independent research may be required if you want to pursue this particular method.
--Pete
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
