[prev in list] [next in list] [prev in thread] [next in thread]
List: freedesktop-xorg
Subject: Re: Multitouch in X - Pointer emulation question ?
From: Patrice B <pbfwdlist () gmail ! com>
Date: 2013-10-23 5:59:36
Message-ID: CALPAzDOVqz4DtdULtn5no7o=OBLerv=Gif0xtSV8VVYNCaZ8=w () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Thanks, I've created a ticket :
https://bugs.freedesktop.org/show_bug.cgi?id=70790
Regards.
Patrice
2013/10/23 Peter Hutterer <peter.hutterer@who-t.net>
> On Wed, Oct 23, 2013 at 07:27:45AM +0200, Patrice B wrote:
> > Ok. Thanks a lot for this answer !
> >
> > Another question about emulated pointer events, I've noticed that with
> > emulated button press, of course if my app does not register for XI 2.2,
> > the .xbutton.subwindow field of the XEvent is always set to zero. If this
> > button press comes from the mouse, this field is correctly set. Is it a
> > bug, a normal behaviour, or is there again something wrong with my apps ?
>
> sounds like bug, in general emulated events should have the same data as
> normal mouse events.
>
> Cheers,
> Peter
>
> > 2013/10/23 Peter Hutterer <peter.hutterer@who-t.net>
> >
> > > On Thu, Oct 17, 2013 at 11:55:24AM +0200, Patrice B wrote:
> > > > Hello,
> > > >
> > > > I'm working on a kernel evdev driver that provides MT events. This
> > > device
> > > > is correctly detected by evdev Xorg driver and I'm able to see MT
> events
> > > > using "xinput text-xi2". I wrote also a small program based on xi2
> which
> > > > makes two rectangles follow my fingers on the screen and it works.
> > > >
> > > > What is a bit "fuzzy" for me is how programs that don't handle XI2
> > > should
> > > > behave with MT driver. I read
> > > >
> http://who-t.blogspot.fr/2011/12/multitouch-in-x-pointer-emulation.html,
> > > > and I thought common application such as xev should received emulated
> > > > classic X events. They don't receive anything in my case. Should
> they ?
> > > > Does something about this emulation needs to be done in kernel
> driver ?
> > >
> > > the server decides which client gets MT and which one gets an emulated
> > > pointer on a per-client basis. your test program that registers for XI
> 2.2
> > > won't see pointer emulation, but xev still should. Last I checked, this
> > > worked here.
> > >
> > > either way, there's nothing you need to do in the kernel driver. if you
> > > speak the MT protocol B, the rest should be handled automatically.
> > >
> > > Cheers,
> > > Peter
> > >
> > >
> > >
>
[Attachment #5 (text/html)]
<div dir="ltr"><div><div>Thanks, I've created a ticket : <a \
href="https://bugs.freedesktop.org/show_bug.cgi?id=70790">https://bugs.freedesktop.org/show_bug.cgi?id=70790</a><br><br></div>Regards.<br><br></div> \
Patrice<br> </div><div class="gmail_extra"><br><br><div \
class="gmail_quote">2013/10/23 Peter Hutterer <span dir="ltr"><<a \
href="mailto:peter.hutterer@who-t.net" \
target="_blank">peter.hutterer@who-t.net</a>></span><br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> <div class="im">On Wed, Oct 23, 2013 at 07:27:45AM +0200, \
Patrice B wrote:<br> > Ok. Thanks a lot for this answer !<br>
><br>
> Another question about emulated pointer events, I've noticed that with<br>
> emulated button press, of course if my app does not register for XI 2.2,<br>
> the .xbutton.subwindow field of the XEvent is always set to zero. If this<br>
> button press comes from the mouse, this field is correctly set. Is it a<br>
> bug, a normal behaviour, or is there again something wrong with my apps ?<br>
<br>
</div>sounds like bug, in general emulated events should have the same data as<br>
normal mouse events.<br>
<br>
Cheers,<br>
Peter<br>
<div class="HOEnZb"><div class="h5"><br>
> 2013/10/23 Peter Hutterer <<a \
href="mailto:peter.hutterer@who-t.net">peter.hutterer@who-t.net</a>><br> ><br>
> > On Thu, Oct 17, 2013 at 11:55:24AM +0200, Patrice B wrote:<br>
> > > Hello,<br>
> > ><br>
> > > I'm working on a kernel evdev driver that provides MT events. \
This<br> > > device<br>
> > > is correctly detected by evdev Xorg driver and I'm able to see MT \
events<br> > > > using "xinput text-xi2". I wrote also a small \
program based on xi2 which<br> > > > makes two rectangles follow my fingers \
on the screen and it works.<br> > > ><br>
> > > What is a bit "fuzzy" for me is how programs that \
don't handle XI2<br> > > should<br>
> > > behave with MT driver. I read<br>
> > > <a href="http://who-t.blogspot.fr/2011/12/multitouch-in-x-pointer-emulation.html" \
target="_blank">http://who-t.blogspot.fr/2011/12/multitouch-in-x-pointer-emulation.html</a>,<br>
> > > and I thought common application such as xev should received \
emulated<br> > > > classic X events. They don't receive anything in my \
case. Should they ?<br> > > > Does something about this emulation needs to \
be done in kernel driver ?<br> > ><br>
> > the server decides which client gets MT and which one gets an emulated<br>
> > pointer on a per-client basis. your test program that registers for XI \
2.2<br> > > won't see pointer emulation, but xev still should. Last I \
checked, this<br> > > worked here.<br>
> ><br>
> > either way, there's nothing you need to do in the kernel driver. if \
you<br> > > speak the MT protocol B, the rest should be handled \
automatically.<br> > ><br>
> > Cheers,<br>
> > Peter<br>
> ><br>
> ><br>
> ><br>
</div></div></blockquote></div><br></div>
_______________________________________________
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: freedesktop-xorg@progressive-comp.com
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic