Struct TapRecognizer 

pub struct TapRecognizer { /* private fields */ }

Recognizes a single tap (pointer down + up without significant movement).

The recognizer is button-aware: it only fires when the press button matches the release button, and only for buttons present in accept. Default accept is ButtonMask::PRIMARY — left-click only — which is what users expect from a “tap” and keeps right-click free for context menus.

Implementations

impl TapRecognizer

pub fn new() -> Self

pub fn max_distance(self, d: f32) -> Self

pub fn accept_buttons(self, mask: impl Into<ButtonMask>) -> Self

Restrict (or extend) the set of buttons that can fire this recognizer. Default is ButtonMask::PRIMARY.

pub fn accept_any_button(self) -> Self

Convenience: accept any pointer button.

Trait Implementations

impl Debug for TapRecognizer

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for TapRecognizer

fn default() -> Self

Returns the “default value” for a type.

impl GestureRecognizer for TapRecognizer

fn process(&mut self, event: &RawPointerEvent) -> GestureResult

Feed a raw pointer event and return the recognition result.

fn reset(&mut self)

Reset the recognizer to its initial state.

fn priority(&self) -> u32

Priority for arbitration when multiple recognizers compete. Higher priority wins.

fn tick(&mut self, _now: Instant) -> GestureResult

Advance any time-driven state (e.g. long-press elapsed timer). Default is a no-op — only recognizers that depend on wall-clock time (like LongPressRecognizer) override this.

fn next_deadline(&self) -> Option<Instant>

Earliest future Instant at which calling GestureRecognizer::tick could transition the recognizer into Recognized or Failed. Returns None when the recognizer is idle or not time-driven. Used by the event loop to schedule a wake-up before a long-press fires.

fn resets_on_peer_recognition(&self) -> bool

Whether this recognizer should be reset when a peer wins arbitration in the same GestureArena::process call. The default is true — winner-take-all, the usual behaviour for mutually exclusive gestures (tap vs drag, long-press vs tap). Multi-tap recognizers (DoubleTapRecognizer, TripleTapRecognizer) override this to false so a DoubleTap firing at click 2 does not wipe the TripleTapRecognizer’s accumulated state before click 3 arrives.