d3160d095d
clutter: Drop ClutterDeviceManager
...
This is mostly replaced by ClutterSeat, which offers a per-seat instead
of a global device abstraction.
https://gitlab.gnome.org/GNOME/mutter/merge_requests/852
2020-01-30 18:11:23 +01:00
467e94f858
clutter: Add ClutterSeat object
...
This object will take most responsibilities away from ClutterDeviceManager,
with the peculiarity that it'll express the per-seat device tree.
https://gitlab.gnome.org/GNOME/mutter/merge_requests/852
2020-01-30 16:28:51 +01:00
160cc9182d
Replace ClutterPoint by graphene_point_t
...
Remove the tests for ClutterPoint since it's
corresponding code moved to private ClutterStage
methods.
https://gitlab.gnome.org/GNOME/mutter/merge_requests/458
2019-10-16 11:38:14 +00:00
47663c7e0f
clutter: Drop no longer necessary API
...
clutter_input_device_get_physical_size was just used for device mapping
heuristics in MetaInputMapper. It now started using the info from udev
on for both backends, so this means this clutter API is no longer
necessary.
https://gitlab.gnome.org/GNOME/mutter/issues/514
2019-03-25 14:08:40 +01:00
df48b94889
clutter: Add API to retrieve the physical size of absolute devices
...
This will be used in upper layers to match abs input devices (touchscreens,
tablets) to the corresponding output.
2018-12-06 14:44:46 +00:00
8c0e13ca7a
clutter: Remove clutter specific version
...
Use the mutter version when something is still needed.
2018-11-06 17:17:36 +01:00
e081bb3921
clutter: Add clutter_input_device_is_grouped call/vfunc
...
This will be used to query grouped devices (eg. tablets and pads)
https://bugzilla.gnome.org/show_bug.cgi?id=779986
2017-03-13 19:34:10 +01:00
d6fc41b73e
clutter: Add function to find out the number of modes for a pad group
...
This is obtained in backend-dependent ways in the upper layers, seems
better to let ClutterInputDevice provide this information.
https://bugzilla.gnome.org/show_bug.cgi?id=771098
2017-02-10 20:11:19 +01:00
9d38ffa6e3
clutter: Add functions to find out mode switch buttons, and their group
...
This is done in the upper layers through backend-dependent ways, seems
better to let ClutterInputDevice provide this information.
https://bugzilla.gnome.org/show_bug.cgi?id=771098
2017-02-10 20:11:19 +01:00
9587a60da4
clutter: Add clutter_input_device_[gs]et_mapping()
...
This function call only applies to tablets, and thus will error
out unless it's called with CLUTTER_TABLET_DEVICEs. This will
allow setting absolute/relative mapping on those on the fly, as
this is optional.
2016-07-22 13:31:09 +02:00
e7e62ee4a4
clutter: Add clutter_input_device_get_device_node()
...
This function is meant to return the device node path (eg. /dev/input/...),
which will be useful to wire up a few things.
2016-07-22 13:31:09 +02:00
81736b1dea
clutter: Add ::n-rings and ::n-strips property to ClutterInputDevice
...
This will only be practical for pads (and maybe generic buttonsets in
the future?), we just need to know the number as the events will also
contain a number as the identificator.
2016-07-22 13:31:09 +02:00
9710e4a8c0
move everything into a clutter/ directory
2016-04-12 20:04:26 +02:00
