[PATCH v5 wayland] protocol: add wl_pointer.frame, axis_source, axis_stop, and axis_discrete

[Daniel Stone]

Hi,

On 19 November 2015 at 01:21, Bill Spitzak <spitzak at gmail.com> wrote:
> On Wed, Nov 18, 2015 at 2:46 PM, Peter Hutterer <peter.hutterer at who-t.net>
> wrote:
>> discrete events are latching for axis events though, they're not just
>> grouped in the same frame, they always precede the axis event. If you have
>> two axis updates in the same frame, the only allowed order is:
>>     axis_discrete
>>     axis
>>     axis_discrete
>>     axis
>>     frame
>>
>> it is not permitted to have:
>>     axis_discrete
>>     axis_discrete
>>     axis
>>     axis
>>     frame
>>
>> Theoretically possible now that we carry the axis information, but that'd
>> require buy-in from all the current reviewers.

Fine by me, and my R-b stands.

> I think you might want to check to see if everybody thinks that is ok,
> because it makes things simpler by only having to talk about frames, and
> removing the latching discussion. I think what is happening is that wayland
> is starting to group events and requests, and is settling on an idea of a
> frame message to delimit the groups, rather than the latching idea.

Grouping and latching are two quite different things, operating in
different directions. As long as they're well-specified, and generally
in keeping with existing precedent, then that's fine.

Cheers,
Daniel