[]Struct gdk::DeviceManager

pub struct DeviceManager(_, _);

In addition to a single pointer and keyboard for user interface input, GDK contains support for a variety of input devices, including graphics tablets, touchscreens and multiple pointers/keyboards interacting simultaneously with the user interface. Such input devices often have additional features, such as sub-pixel positioning information and additional device-dependent information.

In order to query the device hierarchy and be aware of changes in the device hierarchy (such as virtual devices being created or removed, or physical devices being plugged or unplugged), GDK provides DeviceManager.

By default, and if the platform supports it, GDK is aware of multiple keyboard/pointer pairs and multitouch devices. This behavior can be changed by calling gdk_disable_multidevice before Display::open. There should rarely be a need to do that though, since GDK defaults to a compatibility mode in which it will emit just one enter/leave event pair for all devices on a window. To enable per-device enter/leave events and other multi-pointer interaction features, WindowExt::set_support_multidevice must be called on GdkWindows (or gtk_widget_set_support_multidevice on widgets). window. See the WindowExt::set_support_multidevice documentation for more information.

On X11, multi-device support is implemented through XInput 2. Unless gdk_disable_multidevice is called, the XInput 2 DeviceManager implementation will be used as the input source. Otherwise either the core or XInput 1 implementations will be used.

For simple applications that don’t have any special interest in input devices, the so-called “client pointer” provides a reasonable approximation to a simple setup with a single pointer and keyboard. The device that has been set as the client pointer can be accessed via DeviceManager::get_client_pointer.

Conceptually, in multidevice mode there are 2 device types. Virtual devices (or master devices) are represented by the pointer cursors and keyboard foci that are seen on the screen. Physical devices (or slave devices) represent the hardware that is controlling the virtual devices, and thus have no visible cursor on the screen.

Virtual devices are always paired, so there is a keyboard device for every pointer device. Associations between devices may be inspected through Device::get_associated_device.

There may be several virtual devices, and several physical devices could be controlling each of these virtual devices. Physical devices may also be “floating”, which means they are not attached to any virtual device.

Master and slave devices

carlos@sacarino:~$ xinput list
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ Wacom ISDv4 E6 Pen stylus                 id=10   [slave  pointer  (2)]
⎜   ↳ Wacom ISDv4 E6 Finger touch               id=11   [slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad                id=13   [slave  pointer  (2)]
⎜   ↳ TPPS/2 IBM TrackPoint                     id=14   [slave  pointer  (2)]
⎜   ↳ Wacom ISDv4 E6 Pen eraser                 id=16   [slave  pointer  (2)]
⎣ Virtual core keyboard                         id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Video Bus                                 id=7    [slave  keyboard (3)]
    ↳ Sleep Button                              id=8    [slave  keyboard (3)]
    ↳ Integrated Camera                         id=9    [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=12   [slave  keyboard (3)]
    ↳ ThinkPad Extra Buttons                    id=15   [slave  keyboard (3)]

By default, GDK will automatically listen for events coming from all master devices, setting the Device for all events coming from input devices. Events containing device information are EventType::MotionNotify, EventType::ButtonPress, EventType::2buttonPress, EventType::3buttonPress, EventType::ButtonRelease, EventType::Scroll, EventType::KeyPress, EventType::KeyRelease, EventType::EnterNotify, EventType::LeaveNotify, EventType::FocusChange, EventType::ProximityIn, EventType::ProximityOut, EventType::DragEnter, EventType::DragLeave, EventType::DragMotion, EventType::DragStatus, EventType::DropStart, EventType::DropFinished and EventType::GrabBroken. When dealing with an event on a master device, it is possible to get the source (slave) device that the event originated from via gdk_event_get_source_device.

On a standard session, all physical devices are connected by default to the "Virtual Core Pointer/Keyboard" master devices, hence routing all events through these. This behavior is only modified by device grabs, where the slave device is temporarily detached for as long as the grab is held, and more permanently by user modifications to the device hierarchy.

On certain application specific setups, it may make sense to detach a physical device from its master pointer, and mapping it to an specific window. This can be achieved by the combination of Device::grab and Device::set_mode.

In order to listen for events coming from devices other than a virtual device, WindowExt::set_device_events must be called. Generally, this function can be used to modify the event mask for any given device.

Input devices may also provide additional information besides X/Y. For example, graphics tablets may also provide pressure and X/Y tilt information. This information is device-dependent, and may be queried through Device::get_axis. In multidevice mode, virtual devices will change axes in order to always represent the physical device that is routing events through it. Whenever the physical device changes, the Device:n-axes property will be notified, and Device::list_axes will return the new device axes.

Devices may also have associated “keys” or macro buttons. Such keys can be globally set to map into normal X keyboard events. The mapping is set using Device::set_key.

In GTK+ 3.20, a new Seat object has been introduced that supersedes DeviceManager and should be preferred in newly written code.

Implementations

impl DeviceManager[src]

pub fn get_client_pointer(&self) -> Option<Device>[src]

Returns the client pointer, that is, the master pointer that acts as the core pointer for this application. In X11, window managers may change this depending on the interaction pattern under the presence of several pointers.

You should use this function seldomly, only in code that isn’t triggered by a GdkEvent and there aren’t other means to get a meaningful Device to operate on.

Deprecated since 3.20

Use Seat::get_pointer instead.

Returns

The client pointer. This memory is owned by GDK and must not be freed or unreferenced.

pub fn get_display(&self) -> Option<Display>[src]

Gets the Display associated to self.

Returns

the Display to which self is associated to, or None. This memory is owned by GDK and must not be freed or unreferenced.

pub fn list_devices(&self, type_: DeviceType) -> Vec<Device>[src]

Returns the list of devices of type type_ currently attached to self.

Deprecated since 3.20

, use Seat::get_pointer, Seat::get_keyboard and Seat::get_slaves instead.

type_

device type to get.

Returns

a list of GdkDevices. The returned list must be freed with g_list_free (). The list elements are owned by GTK+ and must not be freed or unreffed.

pub fn connect_device_added<F: Fn(&DeviceManager, &Device) + 'static>(
    &self,
    f: F
) -> SignalHandlerId
[src]

The ::device-added signal is emitted either when a new master pointer is created, or when a slave (Hardware) input device is plugged in.

device

the newly added Device.

pub fn connect_device_changed<F: Fn(&DeviceManager, &Device) + 'static>(
    &self,
    f: F
) -> SignalHandlerId
[src]

The ::device-changed signal is emitted whenever a device has changed in the hierarchy, either slave devices being disconnected from their master device or connected to another one, or master devices being added or removed a slave device.

If a slave device is detached from all master devices (Device::get_associated_device returns None), its DeviceType will change to DeviceType::Floating, if it's attached, it will change to DeviceType::Slave.

device

the Device that changed.

pub fn connect_device_removed<F: Fn(&DeviceManager, &Device) + 'static>(
    &self,
    f: F
) -> SignalHandlerId
[src]

The ::device-removed signal is emitted either when a master pointer is removed, or when a slave (Hardware) input device is unplugged.

device

the just removed Device.

impl DeviceManager[src]

pub fn disable_multidevice()[src]

Trait Implementations

impl Clone for DeviceManager

impl Debug for DeviceManager

impl Display for DeviceManager[src]

impl Eq for DeviceManager

impl Hash for DeviceManager

impl Ord for DeviceManager

impl<T: ObjectType> PartialEq<T> for DeviceManager

impl<T: ObjectType> PartialOrd<T> for DeviceManager

impl StaticType for DeviceManager

Auto Trait Implementations

impl RefUnwindSafe for DeviceManager

impl !Send for DeviceManager

impl !Sync for DeviceManager

impl Unpin for DeviceManager

impl UnwindSafe for DeviceManager

Blanket Implementations

impl<T> Any for T where
    T: 'static + ?Sized
[src]

impl<T> Borrow<T> for T where
    T: ?Sized
[src]

impl<T> BorrowMut<T> for T where
    T: ?Sized
[src]

impl<Super, Sub> CanDowncast<Sub> for Super where
    Sub: IsA<Super>,
    Super: IsA<Super>, 

impl<T> Cast for T where
    T: ObjectType, 

impl<T> From<T> for T[src]

impl<T, U> Into<U> for T where
    U: From<T>, 
[src]

impl<T> ObjectExt for T where
    T: ObjectType, 

impl<'a, T> ToGlibContainerFromSlice<'a, *const GList> for T where
    T: GlibPtrDefault + ToGlibPtr<'a, <T as GlibPtrDefault>::GlibType>, 

type Storage = (Option<List>, Vec<Stash<'a, <T as GlibPtrDefault>::GlibType, T>>)

impl<'a, T> ToGlibContainerFromSlice<'a, *const GPtrArray> for T where
    T: GlibPtrDefault + ToGlibPtr<'a, <T as GlibPtrDefault>::GlibType>, 

type Storage = (Option<PtrArray>, Vec<Stash<'a, <T as GlibPtrDefault>::GlibType, T>>)

impl<'a, T> ToGlibContainerFromSlice<'a, *mut GArray> for T where
    T: GlibPtrDefault + ToGlibPtr<'a, <T as GlibPtrDefault>::GlibType>, 

type Storage = (Option<Array>, Vec<Stash<'a, <T as GlibPtrDefault>::GlibType, T>>)

impl<'a, T> ToGlibContainerFromSlice<'a, *mut GList> for T where
    T: GlibPtrDefault + ToGlibPtr<'a, <T as GlibPtrDefault>::GlibType>, 

type Storage = (Option<List>, Vec<Stash<'a, <T as GlibPtrDefault>::GlibType, T>>)

impl<'a, T> ToGlibContainerFromSlice<'a, *mut GPtrArray> for T where
    T: GlibPtrDefault + ToGlibPtr<'a, <T as GlibPtrDefault>::GlibType>, 

type Storage = (Option<PtrArray>, Vec<Stash<'a, <T as GlibPtrDefault>::GlibType, T>>)

impl<T> ToOwned for T where
    T: Clone
[src]

type Owned = T

The resulting type after obtaining ownership.

impl<T> ToSendValue for T where
    T: ToValue + SetValue + Send + ?Sized

impl<T> ToString for T where
    T: Display + ?Sized
[src]

impl<T> ToValue for T where
    T: SetValue + ?Sized

impl<T, U> TryFrom<U> for T where
    U: Into<T>, 
[src]

type Error = Infallible

The type returned in the event of a conversion error.

impl<T, U> TryInto<U> for T where
    U: TryFrom<T>, 
[src]

type Error = <U as TryFrom<T>>::Error

The type returned in the event of a conversion error.