[PATCH weston 21/25] protocol: add weston_touch_calibration

Peter Hutterer peter.hutterer at who-t.net
Thu Apr 26 04:37:02 UTC 2018


On Tue, Apr 24, 2018 at 02:03:41PM +0300, Pekka Paalanen wrote:
> On Wed, 18 Apr 2018 11:30:42 +0300
> Pekka Paalanen <ppaalanen at gmail.com> wrote:
> 
> > On Mon, 16 Apr 2018 13:40:44 +1000
> > Peter Hutterer <peter.hutterer at who-t.net> wrote:
> > 
> > > On Fri, Apr 13, 2018 at 10:51:37AM +0300, Pekka Paalanen wrote:  
> > > >   
> > > > Well, it does touch-downs at least. I think if motion event would end
> > > > up out of range, I'll send cancel event followed by invalid touch.
> > > > Whee, I found use for the cancel event!    
> > > 
> > > The cancel event would also be used for the multitouch-case, right?
> > > If a second touch appears before the first one is fully processed, you also
> > > need to cancel the first touch. Doesn't even need to be intentional by the
> > > user, could be a palm touch or an accidental touch where they're holding the
> > > screen on an edge.  
> > 
> > I hadn't even thought of that, sounds good.
> 
> Actually, I don't have to filter multiple touchpoints in the server.
> The protocol is copied from the wl_touch interface and can handle
> multiple touch points just fine. It can be up to the client to enter a
> denial mode on a second touch down until they are all up.

> Likewise, if the user puts first touch down on a right device, and a
> second touch down on a wrong device which results in a invalid_touch
> event, it can be up to the client to decide whether it accepts the
> first touch or not.
> 
> I'll just have to make the client deal with those.
> 
> Do you see any problem with this?

nope, all good. Sorry, I forgot about the touch ID being in the events...

Cheers,
   Peter


More information about the wayland-devel mailing list