On Mon, 9 Apr 2018 15:49:37 +1000 Peter Hutterer <[email protected]> wrote:
> Hey, look, almost year later and I found this email. In my defence, I was on > an airplane at the time, hence I missed this :) > > This came up in #wayland where pekka linked to it, so I figured I might as > well look through it. > > On Wed, Aug 16, 2017 at 09:19:06PM +0200, Quentin Glidic wrote: > > From: Quentin Glidic <[email protected]> > > > > Signed-off-by: Quentin Glidic <[email protected]> > > --- > > > > As for one-off vs. sustained actions, alternative wording was suggested: > > - one-shot vs. sustained > > - instantaneous vs. sustained > > - immediate vs. driven > > - triggered vs. initiated > > > > unstable/action-binder/README | 4 + > > .../action-binder/action-binder-unstable-v1.xml | 121 > > +++++++++++++++++++++ > > 2 files changed, 125 insertions(+) > > create mode 100644 unstable/action-binder/README > > create mode 100644 unstable/action-binder/action-binder-unstable-v1.xml > > + <event name="triggered"> > > + <description summary="the action triggered"> > > + This event is sent for one-off actions. > > + > > + If a binding would trigger both triggered and started events, the > > + started event must be sent first. > > + </description> > > This almost certainly needs a value, but at that point it gets a bit harder. > The example in the recent #wayland discussion was the wacom tablet pad > strip but this can get more convoluted quickly. A strip has one > value but 2d manipulations (pinch-and-rotate) can have more axes. So maybe > something like > > <event name="value"> > <description summary="the value for the subsequent action"> > This event is sent before started, stopped, or triggered and contains > the value for the subsequent started, stopped, or triggered event. More > than one value event may be sent, a client must accumulate all values > in the order they are sent. The values are namespace/action specific. > </description> > </event> > > It's not any more generic than the rest of the protocol ;) Hi, I'd like to correct my intention when referring to this patch. I assumed that a tablet extension could replicate and modify parts of the action binder protocol for whatever tablet actions would make sense. I didn't expect the action binder protocol would be usable as is for tablet input which needs to be targeted to a wl_surface I presume. But if it would work, fine by me, though it does feel a little far-fetched. Just want to point out, that the action binder protocol has no wl_surface focus as it is meant for global shortcuts... which does not seem to be mentioned in any part, spec or commit message. Thanks, pq
pgptj_Vsw3kM7.pgp
Description: OpenPGP digital signature
_______________________________________________ wayland-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/wayland-devel
