fdo-mirrors/libinput
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/libinput/libinput.git synced 2025-12-20 18:30:06 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
libinput/src/libinput.sym

360 lines
12 KiB
Text
Raw Normal View History

Use symbol versioning This isn't the final 0.8.0 API yet, but we might as well get started. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-12-09 12:52:45 +10:00
/* in alphabetical order! */
Drop libinput_device_has_button And merge all current API versions into the same block. This isn't technically necessary since removing libinput_has_button from the code will remove it from the exported list. That trips up test/symbols-leak-test though. Since we break the API and bump the soname in this release anyway, move to a single block so the initial stable API is all nicely grouped together. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-03-04 15:36:35 +10:00
LIBINPUT_0.12.0 {
Use symbol versioning This isn't the final 0.8.0 API yet, but we might as well get started. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-12-09 12:52:45 +10:00
global:
libinput_config_status_to_str;
libinput_device_config_accel_get_default_speed;
libinput_device_config_accel_get_speed;
libinput_device_config_accel_is_available;
libinput_device_config_accel_set_speed;
libinput_device_config_calibration_get_default_matrix;
libinput_device_config_calibration_get_matrix;
libinput_device_config_calibration_has_matrix;
libinput_device_config_calibration_set_matrix;
Drop libinput_device_has_button And merge all current API versions into the same block. This isn't technically necessary since removing libinput_has_button from the code will remove it from the exported list. That trips up test/symbols-leak-test though. Since we break the API and bump the soname in this release anyway, move to a single block so the initial stable API is all nicely grouped together. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-03-04 15:36:35 +10:00
libinput_device_config_click_get_default_method;
libinput_device_config_click_get_method;
libinput_device_config_click_get_methods;
libinput_device_config_click_set_method;
Sort exported symbols alphabetically Alphabeting is hard... Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-03-06 15:51:49 +10:00
libinput_device_config_left_handed_get;
libinput_device_config_left_handed_get_default;
libinput_device_config_left_handed_is_available;
libinput_device_config_left_handed_set;
Use symbol versioning This isn't the final 0.8.0 API yet, but we might as well get started. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-12-09 12:52:45 +10:00
libinput_device_config_scroll_get_button;
libinput_device_config_scroll_get_default_button;
libinput_device_config_scroll_get_default_method;
libinput_device_config_scroll_get_default_natural_scroll_enabled;
libinput_device_config_scroll_get_method;
Sort exported symbols alphabetically Alphabeting is hard... Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-03-06 15:51:49 +10:00
libinput_device_config_scroll_get_methods;
Use symbol versioning This isn't the final 0.8.0 API yet, but we might as well get started. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-12-09 12:52:45 +10:00
libinput_device_config_scroll_get_natural_scroll_enabled;
libinput_device_config_scroll_has_natural_scroll;
libinput_device_config_scroll_set_button;
libinput_device_config_scroll_set_method;
libinput_device_config_scroll_set_natural_scroll_enabled;
libinput_device_config_send_events_get_default_mode;
libinput_device_config_send_events_get_mode;
Sort exported symbols alphabetically Alphabeting is hard... Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-03-06 15:51:49 +10:00
libinput_device_config_send_events_get_modes;
Use symbol versioning This isn't the final 0.8.0 API yet, but we might as well get started. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-12-09 12:52:45 +10:00
libinput_device_config_send_events_set_mode;
libinput_device_config_tap_get_default_enabled;
libinput_device_config_tap_get_enabled;
libinput_device_config_tap_get_finger_count;
libinput_device_config_tap_set_enabled;
libinput_device_get_context;
Drop libinput_device_has_button And merge all current API versions into the same block. This isn't technically necessary since removing libinput_has_button from the code will remove it from the exported list. That trips up test/symbols-leak-test though. Since we break the API and bump the soname in this release anyway, move to a single block so the initial stable API is all nicely grouped together. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-03-04 15:36:35 +10:00
libinput_device_get_device_group;
Use symbol versioning This isn't the final 0.8.0 API yet, but we might as well get started. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-12-09 12:52:45 +10:00
libinput_device_get_id_product;
libinput_device_get_id_vendor;
libinput_device_get_name;
libinput_device_get_output_name;
libinput_device_get_seat;
libinput_device_get_size;
libinput_device_get_sysname;
libinput_device_get_udev_device;
libinput_device_get_user_data;
Drop libinput_device_has_button And merge all current API versions into the same block. This isn't technically necessary since removing libinput_has_button from the code will remove it from the exported list. That trips up test/symbols-leak-test though. Since we break the API and bump the soname in this release anyway, move to a single block so the initial stable API is all nicely grouped together. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-03-04 15:36:35 +10:00
libinput_device_group_get_user_data;
libinput_device_group_ref;
libinput_device_group_set_user_data;
libinput_device_group_unref;
Use symbol versioning This isn't the final 0.8.0 API yet, but we might as well get started. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-12-09 12:52:45 +10:00
libinput_device_has_capability;
libinput_device_led_update;
Drop libinput_device_has_button And merge all current API versions into the same block. This isn't technically necessary since removing libinput_has_button from the code will remove it from the exported list. That trips up test/symbols-leak-test though. Since we break the API and bump the soname in this release anyway, move to a single block so the initial stable API is all nicely grouped together. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-03-04 15:36:35 +10:00
libinput_device_pointer_has_button;
Use symbol versioning This isn't the final 0.8.0 API yet, but we might as well get started. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-12-09 12:52:45 +10:00
libinput_device_ref;
libinput_device_set_seat_logical_name;
libinput_device_set_user_data;
libinput_device_unref;
libinput_dispatch;
libinput_event_destroy;
libinput_event_device_notify_get_base_event;
libinput_event_get_context;
libinput_event_get_device;
Sort exported symbols alphabetically Alphabeting is hard... Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-03-06 15:51:49 +10:00
libinput_event_get_device_notify_event;
Use symbol versioning This isn't the final 0.8.0 API yet, but we might as well get started. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-12-09 12:52:45 +10:00
libinput_event_get_keyboard_event;
libinput_event_get_pointer_event;
libinput_event_get_touch_event;
libinput_event_get_type;
libinput_event_keyboard_get_base_event;
libinput_event_keyboard_get_key;
Sort exported symbols alphabetically Alphabeting is hard... Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-03-06 15:51:49 +10:00
libinput_event_keyboard_get_key_state;
Use symbol versioning This isn't the final 0.8.0 API yet, but we might as well get started. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-12-09 12:52:45 +10:00
libinput_event_keyboard_get_seat_key_count;
libinput_event_keyboard_get_time;
libinput_event_pointer_get_absolute_x;
libinput_event_pointer_get_absolute_x_transformed;
libinput_event_pointer_get_absolute_y;
libinput_event_pointer_get_absolute_y_transformed;
Add pointer axis sources to the API For a caller to implement/provide kinetic scrolling ("inertial scrolling", "fling scrolling"), it needs to know how the scrolling motion was implemented, and what to expect in the future. Add this information to the pointer axis event. The three scroll sources we have are: * wheels: scrolling is in discreet steps, you don't know when it ends, the wheel will just stop sending events * fingers: scrolling is continuous coordinate space, we know when it stops and we can tell the caller * continuous: scrolling is in continuous coordinate space but we may or may not know when it stops. if scroll lock is used, the device may never technically get out of scroll mode even if it doesn't send events at any given moment Use case: trackpoint/trackball scroll emulation on button press The stop event is now codified in the API documentation, so callers can use that for kinetic scrolling. libinput does not implement kinetic scrolling itself. Not covered by this patch: * The wheel event is currently defined as "typical mouse wheel step", this is different to Qt where the step value is 1/8 of a degree. Some better definition here may help. * It is unclear how an absolute device would map into relative motion if the device itself is not controlling absolute motion. * For diagonal scrolling, the vertical/horizontal terminator events would come in separately. The caller would have to deal with that somehow. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Original patch, before the rebase onto today's master: Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-11-05 16:22:07 +10:00
libinput_event_pointer_get_axis_source;
Use symbol versioning This isn't the final 0.8.0 API yet, but we might as well get started. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-12-09 12:52:45 +10:00
libinput_event_pointer_get_axis_value;
Add libinput_event_pointer_get_axis_value_discrete() to count wheel clicks The recent normalization of wheel events means we get the angle in degrees but we don't know how this corresponds to clicks. The M325 has a 20 degree click angle, most other mice have 15 degrees. So an angle of 60 can be 3 or 4 click events. Most clients care more about the click count than the angle on a mouse wheel. Provide that value when needed. Adding a discrete value to the axis event leaves the possibility of defining discrete units for finger/continuous scroll sources in the future. Right now, these will always reuturn 0. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-01-13 15:15:02 +10:00
libinput_event_pointer_get_axis_value_discrete;
Use symbol versioning This isn't the final 0.8.0 API yet, but we might as well get started. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-12-09 12:52:45 +10:00
libinput_event_pointer_get_base_event;
libinput_event_pointer_get_button;
Sort exported symbols alphabetically Alphabeting is hard... Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-03-06 15:51:49 +10:00
libinput_event_pointer_get_button_state;
Use symbol versioning This isn't the final 0.8.0 API yet, but we might as well get started. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-12-09 12:52:45 +10:00
libinput_event_pointer_get_dx;
libinput_event_pointer_get_dx_unaccelerated;
libinput_event_pointer_get_dy;
libinput_event_pointer_get_dy_unaccelerated;
libinput_event_pointer_get_seat_button_count;
libinput_event_pointer_get_time;
Change axis events to carry all directions Sending separate axis events instead of one unified events is limiting, especially when simultaneously scrolling in both directions and the caller tries to implement kinetic scrolling. Take a page from the tablet-support branch and instead implement the axis event as a generic event that can contain multiple axes simultaneously. Right now we only have two (scroll) axes and we could easily just check both for non-zero values. If we want to allow further axes in the future, we need a check whether an axis is set in an event, that's what libinput_event_pointer_has_axis to scroll events() is for. We also need the mask to notify of a scroll stop event, which could otherwise be confused as a vertical-only or horizontal-only event. This is an API and ABI break. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-12-24 11:10:04 +10:00
libinput_event_pointer_has_axis;
Use symbol versioning This isn't the final 0.8.0 API yet, but we might as well get started. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-12-09 12:52:45 +10:00
libinput_event_touch_get_base_event;
libinput_event_touch_get_seat_slot;
libinput_event_touch_get_slot;
libinput_event_touch_get_time;
libinput_event_touch_get_x;
libinput_event_touch_get_x_transformed;
libinput_event_touch_get_y;
libinput_event_touch_get_y_transformed;
libinput_get_event;
libinput_get_fd;
libinput_get_user_data;
libinput_log_get_priority;
libinput_log_set_handler;
libinput_log_set_priority;
libinput_next_event_type;
libinput_path_add_device;
libinput_path_create_context;
libinput_path_remove_device;
libinput_ref;
libinput_resume;
libinput_seat_get_context;
libinput_seat_get_logical_name;
libinput_seat_get_physical_name;
libinput_seat_get_user_data;
libinput_seat_ref;
libinput_seat_set_user_data;
libinput_seat_unref;
Add libinput_set_user_data Previously, the pointer could only be passed into the context on creation time and was immutable after that. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2014-12-23 13:37:28 +10:00
libinput_set_user_data;
Use symbol versioning This isn't the final 0.8.0 API yet, but we might as well get started. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-12-09 12:52:45 +10:00
libinput_suspend;
libinput_udev_assign_seat;
libinput_udev_create_context;
libinput_unref;
Merge branch 'master' into tablet-support Manual changes: * add tablet APIs to libinput.sym * add the tablet-specific events to litest_event_type_str * add NULL for device_remove in the tablet interface Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2014-12-18 09:39:46 +10:00
Move the tablet functions to the 0.9.0 symbol table Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-01-20 15:32:07 +10:00
local:
*;
};
Add middle mouse button emulation config options Adds the following quartett of functions to enable/disable middle mouse button emulation on a device: libinput_device_config_middle_emulation_is_available() libinput_device_config_middle_emulation_set_enabled() libinput_device_config_middle_emulation_get_enabled() libinput_device_config_middle_emulation_get_default_enabled() This patch only adds the config framework, it is not hooked up to anything yet. Note: like other features this is merely the config option, some devices will provide middle button emulation without exposing it as configuration. i.e. the return value of libinput_device_config_middle_emulation_is_available() only tells you whether you can _configure_ middle button emulation. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-14 12:08:33 +10:00
LIBINPUT_0.14.0 {
global:
Sort the middle button symbols additions correctly Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-04-22 08:20:34 +10:00
libinput_device_config_middle_emulation_get_default_enabled;
libinput_device_config_middle_emulation_get_enabled;
Add middle mouse button emulation config options Adds the following quartett of functions to enable/disable middle mouse button emulation on a device: libinput_device_config_middle_emulation_is_available() libinput_device_config_middle_emulation_set_enabled() libinput_device_config_middle_emulation_get_enabled() libinput_device_config_middle_emulation_get_default_enabled() This patch only adds the config framework, it is not hooked up to anything yet. Note: like other features this is merely the config option, some devices will provide middle button emulation without exposing it as configuration. i.e. the return value of libinput_device_config_middle_emulation_is_available() only tells you whether you can _configure_ middle button emulation. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-04-14 12:08:33 +10:00
libinput_device_config_middle_emulation_is_available;
libinput_device_config_middle_emulation_set_enabled;
} LIBINPUT_0.12.0;
Add libinput_device_keyboard_has_key() Similar to libinput_device_pointer_has_button(), this function returns whether a given device has a specific keycode. This enables a caller to determine if the device is really a keyboard (check for KEY_A-KEY_Z) or just a media key device (check for KEY_PLAY or somesuch), depending on the context required. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com> Reviewed-by: Derek Foreman <derekf@osg.samsung.com>
2015-04-22 14:36:25 +10:00
LIBINPUT_0.15.0 {
global:
libinput_device_keyboard_has_key;
} LIBINPUT_0.14.0;
Merge branch 'master' into tablet-support
2015-05-22 14:21:21 +10:00
Add configuration interface for tap drag-lock In some applications, notably Inkscape, where it is common to frequently drag objects a short distance the default to drag-lock always-on is frustrating for users. Make it configurable, with the current default to "on". New API: libinput_device_config_tap_set_drag_lock_enabled libinput_device_config_tap_get_drag_lock_enabled libinput_device_config_tap_get_default_drag_lock_enabled Any device capable of tapping is capable of drag lock, there is no explicit availability check for drag lock. Configuration is independent, drag lock may be enabled when tapping is disabled. In the tests, enable/disable drag-lock explicitly where the tests depend on it. https://bugs.freedesktop.org/show_bug.cgi?id=90928 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-06-16 17:02:02 +10:00
LIBINPUT_0.19.0 {
Add missing "global" tag to the 0.19 symbol block Not required, but for consistency. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-07-06 11:22:34 +10:00
global:
Add configuration interface for tap drag-lock In some applications, notably Inkscape, where it is common to frequently drag objects a short distance the default to drag-lock always-on is frustrating for users. Make it configurable, with the current default to "on". New API: libinput_device_config_tap_set_drag_lock_enabled libinput_device_config_tap_get_drag_lock_enabled libinput_device_config_tap_get_default_drag_lock_enabled Any device capable of tapping is capable of drag lock, there is no explicit availability check for drag lock. Configuration is independent, drag lock may be enabled when tapping is disabled. In the tests, enable/disable drag-lock explicitly where the tests depend on it. https://bugs.freedesktop.org/show_bug.cgi?id=90928 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-06-16 17:02:02 +10:00
libinput_device_config_tap_set_drag_lock_enabled;
libinput_device_config_tap_get_drag_lock_enabled;
libinput_device_config_tap_get_default_drag_lock_enabled;
} LIBINPUT_0.15.0;
Merge branch 'master' into tablet-support
2015-06-29 13:56:05 +10:00
libinput.sym: make the touchpad gestures part of the 0.20 API Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-07-06 14:10:48 +10:00
LIBINPUT_0.20.0 {
touchpad: Extend the touchpad gesture API with pinch gestures Extend the touchpad gesture API with pinch gestures. Note that this new API offers a single event stream for both pinch and rotate data, this is deliberate as some applications may be interested in getting both at the same time. Applications which are only interested in one or the other can simply ignore the other. Signed-off-by: Hans de Goede <hdegoede@redhat.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Acked-by: Jason Gerecke <jason.gerecke@wacom.com>
2015-03-04 15:24:04 +01:00
libinput_event_gesture_get_angle_delta;
touchpad: Add an API for touchpad gesture events For touchscreens we always send raw touch events to the compositor, and the compositor or application toolkits do gesture recognition. This makes sense because on a touchscreen which window / widget the touches are over is important context to know to interpret gestures. On touchpads however we never send raw events since a touchpad is an absolute device which primary function is to send pointer motion delta-s, so we always need to do processing (and a lot of it) on the raw events. Moreover there is nothing underneath the finger which influences how to interpret gestures, and there is a lot of touchpad and libinput configuration specific context necessary for gesture recognition. E.g. is this a clickpad, and if so are softbuttons or clickfinger used? What is the size of the softbuttons? Is this a true multi-touch touchpad or a semi multi-touch touchpad which only gives us a bounding box enclosing the fingers? Etc. So for touchpads it is better to do gesture processing in libinput, this commit adds an initial implementation of a Gesture event API which only supports swipe gestures, other gestures will be added later following the same model wrt, having clear start and stop events and the number of fingers involved being fixed once a gesture sequence starts. Signed-off-by: Hans de Goede <hdegoede@redhat.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Acked-by: Jason Gerecke <jason.gerecke@wacom.com>
2015-01-22 16:41:50 +01:00
libinput_event_gesture_get_base_event;
touchpad: Allow querying whether a gesture ended normally or was cancelled Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2015-04-29 13:19:51 +02:00
libinput_event_gesture_get_cancelled;
touchpad: Add an API for touchpad gesture events For touchscreens we always send raw touch events to the compositor, and the compositor or application toolkits do gesture recognition. This makes sense because on a touchscreen which window / widget the touches are over is important context to know to interpret gestures. On touchpads however we never send raw events since a touchpad is an absolute device which primary function is to send pointer motion delta-s, so we always need to do processing (and a lot of it) on the raw events. Moreover there is nothing underneath the finger which influences how to interpret gestures, and there is a lot of touchpad and libinput configuration specific context necessary for gesture recognition. E.g. is this a clickpad, and if so are softbuttons or clickfinger used? What is the size of the softbuttons? Is this a true multi-touch touchpad or a semi multi-touch touchpad which only gives us a bounding box enclosing the fingers? Etc. So for touchpads it is better to do gesture processing in libinput, this commit adds an initial implementation of a Gesture event API which only supports swipe gestures, other gestures will be added later following the same model wrt, having clear start and stop events and the number of fingers involved being fixed once a gesture sequence starts. Signed-off-by: Hans de Goede <hdegoede@redhat.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Acked-by: Jason Gerecke <jason.gerecke@wacom.com>
2015-01-22 16:41:50 +01:00
libinput_event_gesture_get_dx;
libinput_event_gesture_get_dx_unaccelerated;
libinput_event_gesture_get_dy;
libinput_event_gesture_get_dy_unaccelerated;
libinput_event_gesture_get_finger_count;
touchpad: Extend the touchpad gesture API with pinch gestures Extend the touchpad gesture API with pinch gestures. Note that this new API offers a single event stream for both pinch and rotate data, this is deliberate as some applications may be interested in getting both at the same time. Applications which are only interested in one or the other can simply ignore the other. Signed-off-by: Hans de Goede <hdegoede@redhat.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Acked-by: Jason Gerecke <jason.gerecke@wacom.com>
2015-03-04 15:24:04 +01:00
libinput_event_gesture_get_scale;
touchpad: Add an API for touchpad gesture events For touchscreens we always send raw touch events to the compositor, and the compositor or application toolkits do gesture recognition. This makes sense because on a touchscreen which window / widget the touches are over is important context to know to interpret gestures. On touchpads however we never send raw events since a touchpad is an absolute device which primary function is to send pointer motion delta-s, so we always need to do processing (and a lot of it) on the raw events. Moreover there is nothing underneath the finger which influences how to interpret gestures, and there is a lot of touchpad and libinput configuration specific context necessary for gesture recognition. E.g. is this a clickpad, and if so are softbuttons or clickfinger used? What is the size of the softbuttons? Is this a true multi-touch touchpad or a semi multi-touch touchpad which only gives us a bounding box enclosing the fingers? Etc. So for touchpads it is better to do gesture processing in libinput, this commit adds an initial implementation of a Gesture event API which only supports swipe gestures, other gestures will be added later following the same model wrt, having clear start and stop events and the number of fingers involved being fixed once a gesture sequence starts. Signed-off-by: Hans de Goede <hdegoede@redhat.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Acked-by: Jason Gerecke <jason.gerecke@wacom.com>
2015-01-22 16:41:50 +01:00
libinput_event_gesture_get_time;
libinput_event_get_gesture_event;
} LIBINPUT_0.19.0;
Merge branch 'master' into tablet-support Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-07-08 13:50:24 +10:00
Add a configuration interface for enabling/disabling disable-while-typing DWT can interfere with some applications where keyboard and touchpad use at the same time is common, e.g. games but also anything that requires a combination of frequent pointer motion and use of keyboard shortcuts. Expose a toggle to disable DWT where needed. https://bugs.freedesktop.org/show_bug.cgi?id=90624 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-07-08 15:03:06 +10:00
LIBINPUT_0.21.0 {
libinput_device_config_dwt_is_available;
libinput_device_config_dwt_set_enabled;
libinput_device_config_dwt_get_enabled;
libinput_device_config_dwt_get_default_enabled;
Change to micro seconds for measuring time internally In order to provide higher precision event time stamps, change the internal time measuring from milliseconds to microseconds. Microseconds are chosen because it is the most fine grained time stamp we can get from evdev. The API is extended with high precision getters whenever the given information is available. Signed-off-by: Jonas Ådahl <jadahl@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-07-27 17:51:52 +08:00
libinput_event_gesture_get_time_usec;
libinput_event_keyboard_get_time_usec;
libinput_event_pointer_get_time_usec;
libinput_event_touch_get_time_usec;
Add a configuration interface for enabling/disabling disable-while-typing DWT can interfere with some applications where keyboard and touchpad use at the same time is common, e.g. games but also anything that requires a combination of frequent pointer motion and use of keyboard shortcuts. Expose a toggle to disable DWT where needed. https://bugs.freedesktop.org/show_bug.cgi?id=90624 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-07-08 15:03:06 +10:00
} LIBINPUT_0.20.0;
Merge branch 'master' into tablet-support
2015-07-24 10:56:05 +10:00
Add an API to change pointer acceleration profiles The quartett of new config functions is: libinput_device_config_accel_get_profiles libinput_device_config_accel_get_profile libinput_device_config_accel_set_profile libinput_device_config_accel_get_default_profile The profile defines how the pointer acceleration works, from a very high-level perspective. Two profiles are on offer, "adaptive", the standard one we have used so far and "flat" which is a simple multiplier of input deltas and provides 1:1 mapping of device movement vs pointer movement. The speed setting is on top of the profile, a speed of 0 (default) is the equivalent to "no pointer acceleration". This is popular among gamers and users of switchable-dpi mice. The flat profile unnormalizes the deltas, i.e. you get what the device does and any device below 800dpi will feel excruciatingly slow. The speed range [-1, 1] maps into 0-200% of the speed. At 200%, a delta of 1 is translated into a 2 pixel movement, anything higher makes it rather pointless. The flat profile is currently available for all pointer devices but touchpads. https://bugs.freedesktop.org/show_bug.cgi?id=89485 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-08-27 13:13:47 +10:00
LIBINPUT_1.1 {
libinput_device_config_accel_get_profile;
libinput_device_config_accel_get_profiles;
libinput_device_config_accel_get_default_profile;
libinput_device_config_accel_set_profile;
} LIBINPUT_0.21.0;
Merge branch 'master' into tablet-support
2015-10-21 19:19:01 +10:00
touchpad: add a config option to disable tap-and-drag There are a number of use-cases where tapping may be desirable, but tap-and-drag is not, e.g. where tapping is used to select multiple items in a list. Having tap-and-drag on hinders this, and the nature of the interaction means it cannot be detected based on timeouts, movement thresholds, etc. Provide an option instead to turn tap-an-drag off. Tap-and-drag remains enabled by default (though tapping is disabled by default). For the touchpad tap state diagram, the new option disables the transition from state TOUCH to state TAPPED and releases the button immediately instead. This means that multitap-and-drag is disabled too since we now just loop around in the single-tap state for multitap. It also makes tapping more responsive - we don't have to wait for the timeout before we know whether it's a tap event. The first touch time is noted, we now send the button press with the time of the first touch and the release with the time of the release. This ensures a realistic time diff between the two events. https://bugs.freedesktop.org/show_bug.cgi?id=93502 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.netto> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2016-01-22 17:59:19 +10:00
LIBINPUT_1.2 {
libinput_device_config_tap_get_drag_enabled;
libinput_device_config_tap_get_default_drag_enabled;
libinput_device_config_tap_set_drag_enabled;
tablet: rename libinput_event_tablet to libinput_event_tablet_tool Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-11-16 16:28:55 +10:00
libinput_event_get_tablet_tool_event;
tablet: rename axis_has_changed into an axis-specific API set First part of the big revamp to get rid of libinput_tablet_tool_axis and replace it with a set of axis-specific APIs. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Acked-by: Hans de Goede <hdegoede@redhat.com> Reviewed-by: Lyude <cpaul@redhat.com>
2015-12-14 09:05:37 +10:00
libinput_event_tablet_tool_x_has_changed;
libinput_event_tablet_tool_y_has_changed;
libinput_event_tablet_tool_pressure_has_changed;
libinput_event_tablet_tool_distance_has_changed;
libinput_event_tablet_tool_rotation_has_changed;
libinput_event_tablet_tool_tilt_x_has_changed;
libinput_event_tablet_tool_tilt_y_has_changed;
libinput_event_tablet_tool_wheel_has_changed;
libinput_event_tablet_tool_slider_has_changed;
tablet: add support for relative x/y motion deltas Instead of an explicit tablet mode that device must be changed into, let the caller decide which coordinates are preferred. The tablet mode may be application-specific and usually depends on the tool as well. This patch adds an interface to get a motion delta for the x/y axes in pixel-like coordinates. libinput provides some magic to convert the tablet data into something that resembles pixels from a mouse motion. For unaccelerated relative motion, the caller should use the mm values from the tablet and calculate deltas manually. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Acked-by: Jason Gerecke <jason.gerecke@wacom.com>
2016-01-06 14:47:18 +10:00
libinput_event_tablet_tool_get_dx;
libinput_event_tablet_tool_get_dy;
tablet: rename axis_get_value into an axis-specific API set Second part of the big revamp to get rid of libinput_tablet_tool_axis and replace it with a set of axis-specific APIs. Note that this commit drops the ability to get the absolute value from a relative wheel. The previous API always returned 0 for this case, it is not needed anymore. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Acked-by: Hans de Goede <hdegoede@redhat.com> Reviewed-by: Lyude <cpaul@redhat.com>
2015-12-14 09:51:11 +10:00
libinput_event_tablet_tool_get_x;
libinput_event_tablet_tool_get_y;
libinput_event_tablet_tool_get_pressure;
libinput_event_tablet_tool_get_distance;
libinput_event_tablet_tool_get_tilt_x;
libinput_event_tablet_tool_get_tilt_y;
libinput_event_tablet_tool_get_rotation;
libinput_event_tablet_tool_get_slider_position;
tablet: reduce event deltas to only apply to the wheel Part of the big revamp to get rid of libinput_tablet_tool_axis and replace it with a set of axis-specific APIs. Only the rel wheel has true delta events, everything else is a delta calculated by libinput based on the previous position. Since we supply that position to the callers anyway, they can determine that delta themselves where needed. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Acked-by: Hans de Goede <hdegoede@redhat.com> Reviewed-by: Lyude <cpaul@redhat.com>
2015-12-14 10:23:56 +10:00
libinput_event_tablet_tool_get_wheel_delta;
libinput_event_tablet_tool_get_wheel_delta_discrete;
tablet: rename libinput_event_tablet to libinput_event_tablet_tool Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-11-16 16:28:55 +10:00
libinput_event_tablet_tool_get_base_event;
libinput_event_tablet_tool_get_button;
libinput_event_tablet_tool_get_button_state;
libinput_event_tablet_tool_get_proximity_state;
libinput_event_tablet_tool_get_seat_button_count;
libinput_event_tablet_tool_get_time;
libinput_event_tablet_tool_get_tip_state;
libinput_event_tablet_tool_get_tool;
libinput_event_tablet_tool_get_x_transformed;
libinput_event_tablet_tool_get_y_transformed;
libinput_event_tablet_tool_get_time_usec;
tablet: rename the libinput_tool calls to libinput_tablet_tool Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-11-16 16:35:03 +10:00
libinput_tablet_tool_get_serial;
libinput_tablet_tool_get_tool_id;
libinput_tablet_tool_get_type;
libinput_tablet_tool_get_user_data;
tablet: rename libinput_tablet_tool_has_axis into an axis-specific API set Part of the big revamp to get rid of libinput_tablet_tool_axis and replace it with a set of axis-specific APIs. Note that this commit drops the ability to check whether a tablet has an x or y axis. If it doesn't, libinput won't initialize the tablet anyway so this was superfluous already. Likewise with the tilt axes - either we have x and y tilt or we have neither, so separate checks for tilt_x and tilt_y is unnecessary. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Acked-by: Hans de Goede <hdegoede@redhat.com> Reviewed-by: Lyude <cpaul@redhat.com>
2015-12-14 10:06:56 +10:00
libinput_tablet_tool_has_pressure;
libinput_tablet_tool_has_distance;
libinput_tablet_tool_has_rotation;
libinput_tablet_tool_has_tilt;
libinput_tablet_tool_has_wheel;
libinput_tablet_tool_has_slider;
tablet: rename the libinput_tool calls to libinput_tablet_tool Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-11-16 16:35:03 +10:00
libinput_tablet_tool_has_button;
tablet: add libinput_tablet_tool_is_unique() For checking if a tablet tool can be uniquely identified by libinput. In practice this means checking for a nonzero serial number, but let's not restrict ourselves to allowing just that. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-12-15 12:39:52 +10:00
libinput_tablet_tool_is_unique;
tablet: rename the libinput_tool calls to libinput_tablet_tool Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-11-16 16:35:03 +10:00
libinput_tablet_tool_ref;
libinput_tablet_tool_set_user_data;
libinput_tablet_tool_unref;
Prepare tablet-support branch for merging Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2016-01-27 15:38:47 +10:00
} LIBINPUT_1.1;
Add the LIBINPUT_DEVICE_CAP_TABLET_PAD capability and matching interface This interface handles the buttons on the physical tablet itself, including the touch ring and the strip. A notable difference to other libinput interfaces here is that we do not use linux/input.h event codes for buttons. Instead, the buttons are merely numbered sequentially, starting at button 1. This means: * the API is different, instead of get_button() we have get_button_number() to drive the point home * there is no seat button count. pads are inherently different devices and compositors should treat them as such. The seat button count makes sense when you want to know how many devices have BTN_LEFT down, but it makes no sense for buttons where all the semantics are handled by the compositor anyway. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jason Gerecke <jason.gerecke@wacom.com> Reviewed-by: Carlos Garnacho <carlosg@gnome.org>
2016-01-21 12:35:11 +10:00
Merge branch 'wip/tablet-pad-support'
2016-04-18 13:31:46 +10:00
LIBINPUT_1.3 {
Add the LIBINPUT_DEVICE_CAP_TABLET_PAD capability and matching interface This interface handles the buttons on the physical tablet itself, including the touch ring and the strip. A notable difference to other libinput interfaces here is that we do not use linux/input.h event codes for buttons. Instead, the buttons are merely numbered sequentially, starting at button 1. This means: * the API is different, instead of get_button() we have get_button_number() to drive the point home * there is no seat button count. pads are inherently different devices and compositors should treat them as such. The seat button count makes sense when you want to know how many devices have BTN_LEFT down, but it makes no sense for buttons where all the semantics are handled by the compositor anyway. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jason Gerecke <jason.gerecke@wacom.com> Reviewed-by: Carlos Garnacho <carlosg@gnome.org>
2016-01-21 12:35:11 +10:00
libinput_device_tablet_pad_get_num_buttons;
libinput_device_tablet_pad_get_num_rings;
libinput_device_tablet_pad_get_num_strips;
libinput_event_get_tablet_pad_event;
libinput_event_tablet_pad_get_base_event;
libinput_event_tablet_pad_get_button_number;
libinput_event_tablet_pad_get_button_state;
libinput_event_tablet_pad_get_ring_position;
libinput_event_tablet_pad_get_ring_number;
libinput_event_tablet_pad_get_ring_source;
libinput_event_tablet_pad_get_strip_position;
libinput_event_tablet_pad_get_strip_number;
libinput_event_tablet_pad_get_strip_source;
libinput_event_tablet_pad_get_time;
libinput_event_tablet_pad_get_time_usec;
} LIBINPUT_1.2;
Add support for relative device rotation (trackball only) Trackballs are effectively stationary devices and can be positioned at any rotation. They are also employed by users with impaired dexterity which sometimes implies that they are positioned at an non-default angle to make the buttons easier to reach. Add a config option for rotation for trackball devices. Currently only supported for 90-degree angles, if there is a need we can add more angles later. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2016-05-03 13:52:53 +10:00
LIBINPUT_1.4 {
libinput_device_config_rotation_get_angle;
libinput_device_config_rotation_get_default_angle;
libinput_device_config_rotation_is_available;
libinput_device_config_rotation_set_angle;
pad: Add a new API for modes and mode groups Move mode control to libinput. This reduces some flexibility on what we can do with modes but makes it a lot easier for anyone to implement modes correctly and have the LEDs apply appropriately, etc. Let's go with the option to make the 95% use-case easy. Note: whether the mode is actually used is up to the caller, e.g. under Windows and OS X the mode only applies to the rings/strips, not the buttons. A tablet pad has 1 or more mode groups, all buttons/ring/strips are assigned to a mode group. That group has a numeric mode index and is hooked to the LEDs. libinput will switch the LEDs accordingly. The mode group is a separate object. This allows for better APIs when it comes to: * checking whether a button/ring/strip is part of a mode group * checking whether a button will trigger a mode transition and in the future potentially: * checking which mode transition will happen * setting which button should change the mode transition * changing what type of mode transition should happen. * moving a button from one mode group to the other This patch adds the basic scaffolding, without any real implementation. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Proofread-by: Yong Bakos <ybakos@humanoriented.com> Reviewed-by: Jason Gerecke <jason.gerecke@wacom.com> Reviewed-by: Carlos Garnacho <carlosg@gnome.org>
2016-05-26 10:05:10 +10:00
libinput_device_tablet_pad_get_mode_group;
libinput_device_tablet_pad_get_num_mode_groups;
libinput_event_tablet_pad_get_mode;
libinput_event_tablet_pad_get_mode_group;
libinput_tablet_pad_mode_group_button_is_toggle;
libinput_tablet_pad_mode_group_get_index;
libinput_tablet_pad_mode_group_get_mode;
libinput_tablet_pad_mode_group_get_num_modes;
libinput_tablet_pad_mode_group_get_user_data;
libinput_tablet_pad_mode_group_has_button;
libinput_tablet_pad_mode_group_has_strip;
libinput_tablet_pad_mode_group_has_ring;
libinput_tablet_pad_mode_group_ref;
libinput_tablet_pad_mode_group_set_user_data;
libinput_tablet_pad_mode_group_unref;
Add support for relative device rotation (trackball only) Trackballs are effectively stationary devices and can be positioned at any rotation. They are also employed by users with impaired dexterity which sometimes implies that they are positioned at an non-default angle to make the buttons easier to reach. Add a config option for rotation for trackball devices. Currently only supported for 90-degree angles, if there is a need we can add more angles later. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2016-05-03 13:52:53 +10:00
} LIBINPUT_1.3;
Add configurable button map to tappings The previously hardcoded button map for tapping is 1/2/3 to LRM. But the middle button is a common feature on the desktop (used for paste, most prominently) and three-finger tapping is almost impossible to do reliably on some touchpads (e.g. the T440 has a recognition rate of ~1 in 5). Left and right buttons have a prominent physical position (either softbuttons or physical buttons) so make the tap order configurable. Those that require middle buttons reliably can use the [software] buttons for left/right and 2-finger tap for a middle button. https://bugs.freedesktop.org/show_bug.cgi?id=96962 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2016-07-21 11:46:05 +10:00
LIBINPUT_1.5 {
libinput_device_config_tap_get_button_map;
libinput_device_config_tap_get_default_button_map;
libinput_device_config_tap_set_button_map;
} LIBINPUT_1.4;
Add a "switch" interface for parts of the SW_* range This will allow switch devices known to libinput to be exposed. Currently, this is SW_LID. libinput also handles switch events internally, e.g. a laptop touchpad will be disabled autmoatically when the lid is closed. This is transparent to the caller, although the caller will also receive the event. See https://bugs.freedesktop.org/show_bug.cgi?id=86223 This features is intended to be the main driver for the interface. Co-Authored-By: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: James Ye <jye836@gmail.com> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2017-01-20 16:54:13 +11:00
configure.ac: libinput 1.7rc1 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2017-02-23 10:49:11 +10:00
LIBINPUT_1.7 {
Add a "switch" interface for parts of the SW_* range This will allow switch devices known to libinput to be exposed. Currently, this is SW_LID. libinput also handles switch events internally, e.g. a laptop touchpad will be disabled autmoatically when the lid is closed. This is transparent to the caller, although the caller will also receive the event. See https://bugs.freedesktop.org/show_bug.cgi?id=86223 This features is intended to be the main driver for the interface. Co-Authored-By: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: James Ye <jye836@gmail.com> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2017-01-20 16:54:13 +11:00
libinput_event_get_switch_event;
libinput_event_switch_get_base_event;
libinput_event_switch_get_switch_state;
libinput_event_switch_get_switch;
libinput_event_switch_get_time;
libinput_event_switch_get_time_usec;
} LIBINPUT_1.5;
Add libinput_device_switch_has_switch() Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2017-04-21 16:57:39 +10:00
LIBINPUT_1.9 {
libinput_device_switch_has_switch;
} LIBINPUT_1.7;
Add libinput_device_touch_get_touch_count() This makes it possible for callers to detect whether a touch device is single or multitouch (or even check for things like dual-touch vs real multi-touch) and adjust the interface accordingly. Note that this is for touch devices only, not touchpads that are just pointer devices. https://bugs.freedesktop.org/show_bug.cgi?id=104867 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2018-01-31 16:04:09 +10:00
LIBINPUT_1.11 {
libinput_device_touch_get_touch_count;
} LIBINPUT_1.9;
tablet: add a the Totem tool type to the tablet interface This is the public API only, not the internal bits, so nothing will work just yet. This interface addition is for the Dell Canvas Totem tool, so let's go with the same name because options like "Rotary" are too ambiguous. The totem is a knob that can be placed on the surface, it provides us with location and rotation data. The touch major/minor fields are filled in by the current totem, but they're always the same size. The totem exports BTN_0 as well, so let's add that to the debug-events output. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2018-09-13 13:26:22 +10:00
LIBINPUT_1.14 {
libinput_tablet_tool_has_size;
libinput_event_tablet_tool_get_size_major;
libinput_event_tablet_tool_get_size_minor;
libinput_event_tablet_tool_size_major_has_changed;
libinput_event_tablet_tool_size_minor_has_changed;
} LIBINPUT_1.11;
Add a scroll button lock feature Scroll button locking is an accessibility feature. When enabled, the scroll button does not need to be held down, the first click holds it logically down, to be released on the second click of that same button. This is implemented as simple event filter, so we still get the same behavior from the emulated logical button, i.e. a physical double click results in a single logical click of that button provided no scrolling was triggered. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2019-03-20 10:56:51 +10:00
LIBINPUT_1.15 {
libinput_device_config_scroll_set_button_lock;
libinput_device_config_scroll_get_button_lock;
libinput_device_config_scroll_get_default_button_lock;
pad: add LIBINPUT_EVENT_TABLET_PAD_KEY for pad keys The Wacom Cintiq 24HD and later tablets send specific key events for hardware/soft buttons. KEY_PROG1..KEY_PROG3 on earlier tablets, KEY_CONTROLPANEL, KEY_ONSCREEN_DISPLAY, and KEY_BUTTONCONFIG on later tablets. We ignore KEY_PROG1-3 because starting with kernel 5.4 older tablets will too use the better-named #defines. These differ from pad buttons as the key code in itself carries semantic information, so we should pass them on as-is instead of mapping them to meaningless 0-indexed buttons like we do on the other buttons. So let's add a new event, LIBINPUT_EVENT_TABLET_PAD_KEY and the associated functions to handle that case. Pad keys have a fixed hw-defined semantic meaning and are thus not part of a tablet mode group. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2019-01-17 11:08:27 +10:00
libinput_device_tablet_pad_has_key;
libinput_event_tablet_pad_get_key;
libinput_event_tablet_pad_get_key_state;
Add a scroll button lock feature Scroll button locking is an accessibility feature. When enabled, the scroll button does not need to be held down, the first click holds it logically down, to be released on the second click of that same button. This is implemented as simple event filter, so we still get the same behavior from the emulated logical button, i.e. a physical double click results in a single logical click of that button provided no scrolling was triggered. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2019-03-20 10:56:51 +10:00
} LIBINPUT_1.14;
High-resolution scroll wheel support Starting with kernel v5.0 two new axes are available for high-resolution wheel scrolling: REL_WHEEL_HI_RES and REL_HWHEEL_HI_RES. Both axes send data in fractions of 120 where each multiple of 120 amounts to one logical scroll event. Fractions of 120 indicate a wheel movement less than one detent. This commit adds a new API for scroll events. Three new event types that encode the axis source in the event type name and a new API to get a normalized-to-120 value that also used by Windows and the kernel (each multiple of 120 represents a logical scroll click). This addresses a main shortcoming with the existing API - it was unreliable to calculate the click angle based on the axis value+discrete events and thus any caller using the axis value alone would be left with some ambiguity. With the v120 API it's now possible to (usually) calculate the click angle, but more importantly it provides the simplest hw-independent way of scrolling by a click or a fraction of a click. A new event type is required, the only way to integrate the v120 value otherwise was to start sending events with a discrete value of 0. This would break existing xf86-input-libinput (divide by zero, fixed in 0.28.2) and weston (general confusion). mutter, kwin are unaffected. With the new API, the old POINTER_AXIS event are deprecated - callers should use the new API where available and discard any POINTER_AXIS events. Notable: REL_WHEEL/REL_HWHEEL are emulated by the kernel but there's no guarantee that they'll come every accumulated 120 values, e.g. Logitech mice often send events that don't add up to 120 per detent. We use the kernel's wheel click emulation instead of doing our own. libinput guarantees high-resolution events even on pre-5.0 kernels. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: José Expósito <jose.exposito89@gmail.com>
2018-11-22 10:24:54 +10:00
LIBINPUT_1.19 {
libinput_event_pointer_get_scroll_value_v120;
libinput_event_pointer_get_scroll_value;
} LIBINPUT_1.15;
touchpad: new option dwtp (disable-while-trackpointing) Add option to control whether the touchpad should be disabled while the trackpoint is in use. Fix #731 Signed-off-by: pudiva chip líquida <pudiva@skylittlesystem.org>
2022-03-08 01:33:40 +00:00
LIBINPUT_1.21 {
libinput_device_config_dwtp_is_available;
libinput_device_config_dwtp_set_enabled;
libinput_device_config_dwtp_get_enabled;
libinput_device_config_dwtp_get_default_enabled;
} LIBINPUT_1.19;
Introduce custom acceleration profile The custom acceleration profile allow the user to define custom acceleration functions for each movement type per device, giving full control over accelerations behavior at different speeds. This commit introduces 2 movement types which corresponds to the 2 profiles currently in use by libinput. regular filter is Motion type. constant filter is Fallback type. This allows possible expansion of new movement types for the different devices. The custom pointer acceleration profile gives the user full control over the acceleration behavior at different speeds. The user needs to provide a custom acceleration function f(x) where the x-axis is the device speed and the y-axis is the pointer speed. The user should take into account the native device dpi and screen dpi in order to achieve the desired behavior/feel of the acceleration. The custom acceleration function is defined using n points which are spaced uniformly along the x-axis, starting from 0 and continuing in constant steps. There by the points defining the custom function are: (0 * step, f[0]), (1 * step, f[1]), ..., ((n-1) * step, f[n-1]) where f is a list of n unitless values defining the acceleration factor for each velocity. When a velocity value does not lie exactly on those points, a linear interpolation of the two closest points will be calculated. When a velocity value is greater than the max point defined, a linear extrapolation of the two biggest points will be calculated. Signed-off-by: Yinon Burgansky <51504-Yinon@users.noreply.gitlab.freedesktop.org> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2022-12-13 00:23:59 +02:00
LIBINPUT_1.23 {
libinput_config_accel_create;
libinput_config_accel_destroy;
libinput_device_config_accel_apply;
libinput_config_accel_set_points;
tablet: add tablet tool pressure range configuration Add a configuration option to reduce the available hardware range to a fraction thereof. This is done by copying the absinfo struct for the pressure value and adjusting that copy's minimum/maximum value for scaling into the target normalized range. The 1%/5% tip thresholds are kept but pressure offset detection is disabled if there is a custom pressure range. Unlike the pressure curve which is implemented in the compositor, the pressure min/max range needs to be in libinput, primarily because the tip threshold needs to adjust to any new minimum, allowing for light touches with a pen without triggering tip down even at a higher hardware pressure.
2024-01-15 17:07:17 +10:00
} LIBINPUT_1.21;
LIBINPUT_1.26 {
editorconfig: add settings for sym files Signed-off-by: José Expósito <jose.exposito89@gmail.com> Part-of: <https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/1076>
2024-11-04 10:25:00 +01:00
libinput_device_config_click_set_clickfinger_button_map;
libinput_device_config_click_get_default_clickfinger_button_map;
libinput_device_config_click_get_clickfinger_button_map;
libinput_device_get_id_bustype;
libinput_device_tablet_pad_get_num_dials;
libinput_event_tablet_pad_get_dial_delta_v120;
libinput_event_tablet_pad_get_dial_number;
libinput_tablet_pad_mode_group_has_dial;
libinput_tablet_tool_config_pressure_range_is_available;
libinput_tablet_tool_config_pressure_range_set;
libinput_tablet_tool_config_pressure_range_get_minimum;
libinput_tablet_tool_config_pressure_range_get_maximum;
libinput_tablet_tool_config_pressure_range_get_default_minimum;
libinput_tablet_tool_config_pressure_range_get_default_maximum;
tablet: add tablet tool pressure range configuration Add a configuration option to reduce the available hardware range to a fraction thereof. This is done by copying the absinfo struct for the pressure value and adjusting that copy's minimum/maximum value for scaling into the target normalized range. The 1%/5% tip thresholds are kept but pressure offset detection is disabled if there is a custom pressure range. Unlike the pressure curve which is implemented in the compositor, the pressure min/max range needs to be in libinput, primarily because the tip threshold needs to adjust to any new minimum, allowing for light touches with a pen without triggering tip down even at a higher hardware pressure.
2024-01-15 17:07:17 +10:00
} LIBINPUT_1.23;
Add tablet area configuration This adds the configuration option to define a rectangle that serves as an input area on external tablets such as an Intuos. The intention behind this is to make this input area behave as if it was the only physical input area on this tablet with libinput emulating proximity events as required for where the tools moves in and out of this area. This could also be achieved with the existing calibration setting but area configuration is not calibration and we don't want to expose other side-effects of the matrix (e.g. scaling and rotation) for these devices. Part-of: <https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/1013>
2024-06-13 09:00:21 +10:00
LIBINPUT_1.27 {
libinput_device_config_area_has_rectangle;
libinput_device_config_area_set_rectangle;
libinput_device_config_area_get_rectangle;
libinput_device_config_area_get_default_rectangle;
} LIBINPUT_1.26;
Reference in a new issue Copy permalink