Touch events (was: Towards 1.0)

[Kristian Høgsberg]

2012/2/20 Chase Douglas <chase.douglas at canonical.com>:
> On 02/17/2012 06:01 PM, Kristian Høgsberg wrote:
>>  - input protocol restructuring: break up events into wl_pointer
>> (enter/leave/motion/button/axis events, set_pointer_surface request),
>> wl_keyboard (enter/leave/key events... what else... unicode event,
>> set_map request? pending kb work), and wl_touch (down/up/motion/cancel
>> events) interfaces
>
> [snip]
>
> So the client window will receive touch events without delay, but may
> receive a cancel? I am in favor of this approach, but you need to add a
> way to tell the window when the window manager has "rejected" a touch
> sequence as well. Otherwise the client will never know when they can
> perform destructive operations with it.

No, we don't need that.  Don't do destructive operations on something
that could be the first half on a globall gesture.  If you need to
know for sure that nobody is going to take over the events, wait until
the touch session is over (all touch points up, none cancelled).

Kristian