Trait wayland_protocols::unstable::tablet::v2::client::zwp_tablet_pad_strip_v2::EventHandler

pub trait EventHandler {
    fn source(&mut self, object: ZwpTabletPadStripV2, source: Source) { ... }
    fn position(&mut self, object: ZwpTabletPadStripV2, position: u32) { ... }
    fn stop(&mut self, object: ZwpTabletPadStripV2) { ... }
    fn frame(&mut self, object: ZwpTabletPadStripV2, time: u32) { ... }
}

An interface for handling events.

Provided methods

fn source(&mut self, object: ZwpTabletPadStripV2, source: Source)

strip event source

Source information for strip events.

This event does not occur on its own. It is sent before a wp_tablet_pad_strip.frame event and carries the source information for all events within that frame.

The source specifies how this event was generated. If the source is wp_tablet_pad_strip.source.finger, a wp_tablet_pad_strip.stop event will be sent when the user lifts their finger off the device.

This event is optional. If the source is unknown for an interaction, no event is sent.

fn position(&mut self, object: ZwpTabletPadStripV2, position: u32)

position changed

Sent whenever the position on a strip changes.

The position is normalized to a range of [0, 65535], the 0-value represents the top-most and/or left-most position of the strip in the pad's current rotation.

fn stop(&mut self, object: ZwpTabletPadStripV2)

interaction stopped

Stop notification for strip events.

For some wp_tablet_pad_strip.source types, a wp_tablet_pad_strip.stop event is sent to notify a client that the interaction with the strip has terminated. This enables the client to implement kinetic scrolling. See the wp_tablet_pad_strip.source documentation for information on when this event may be generated.

Any wp_tablet_pad_strip.position events with the same source after this event should be considered as the start of a new interaction.

fn frame(&mut self, object: ZwpTabletPadStripV2, time: u32)

end of a strip event sequence

Indicates the end of a set of events that represent one logical hardware strip event. A client is expected to accumulate the data in all events within the frame before proceeding.

All wp_tablet_pad_strip events before a wp_tablet_pad_strip.frame event belong logically together. For example, on termination of a finger interaction on a strip the compositor will send a wp_tablet_pad_strip.source event, a wp_tablet_pad_strip.stop event and a wp_tablet_pad_strip.frame event.

A wp_tablet_pad_strip.frame event is sent for every logical event group, even if the group only contains a single wp_tablet_pad_strip event. Specifically, a client may get a sequence: position, frame, position, frame, etc.

Loading content...

Implementors

Loading content...