2012-05-17 12:18:17 +02:00
|
|
|
/*
|
|
|
|
|
* Copyright © 2012 Jonas Ådahl
|
2015-05-28 08:23:59 +10:00
|
|
|
* Copyright © 2014-2015 Red Hat, Inc.
|
2012-05-17 12:18:17 +02:00
|
|
|
*
|
2015-06-11 12:09:18 +10:00
|
|
|
* Permission is hereby granted, free of charge, to any person obtaining a
|
|
|
|
|
* copy of this software and associated documentation files (the "Software"),
|
|
|
|
|
* to deal in the Software without restriction, including without limitation
|
|
|
|
|
* the rights to use, copy, modify, merge, publish, distribute, sublicense,
|
|
|
|
|
* and/or sell copies of the Software, and to permit persons to whom the
|
|
|
|
|
* Software is furnished to do so, subject to the following conditions:
|
2012-05-17 12:18:17 +02:00
|
|
|
*
|
2015-06-11 12:09:18 +10:00
|
|
|
* The above copyright notice and this permission notice (including the next
|
|
|
|
|
* paragraph) shall be included in all copies or substantial portions of the
|
|
|
|
|
* Software.
|
|
|
|
|
*
|
|
|
|
|
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
|
|
|
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
|
|
|
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
|
|
|
|
|
* THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
|
|
|
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
|
|
|
|
|
* FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
|
|
|
|
|
* DEALINGS IN THE SOFTWARE.
|
2012-05-17 12:18:17 +02:00
|
|
|
*/
|
|
|
|
|
|
2013-11-10 17:55:40 +01:00
|
|
|
#ifndef FILTER_H
|
|
|
|
|
#define FILTER_H
|
2012-05-17 12:18:17 +02:00
|
|
|
|
2013-08-15 01:10:24 +01:00
|
|
|
#include "config.h"
|
|
|
|
|
|
2014-07-03 15:53:56 +10:00
|
|
|
#include <stdbool.h>
|
2014-07-04 10:43:52 +10:00
|
|
|
#include <stdint.h>
|
|
|
|
|
|
2015-03-19 11:02:51 +10:00
|
|
|
#include "libinput-private.h"
|
2012-05-17 12:18:17 +02:00
|
|
|
|
2013-11-10 17:55:40 +01:00
|
|
|
struct motion_filter;
|
2012-05-17 12:18:17 +02:00
|
|
|
|
2015-08-17 16:32:20 +10:00
|
|
|
/**
|
|
|
|
|
* Accelerate the given coordinates.
|
|
|
|
|
* Takes a set of unaccelerated deltas and accelerates them based on the
|
|
|
|
|
* current and previous motion.
|
|
|
|
|
*
|
|
|
|
|
* This is a superset of filter_dispatch_constant()
|
|
|
|
|
*
|
filter: change the filter functions to take raw device coordinates
We used to normalize all deltas to equivalents of a 1000dpi mouse before
passing it into the acceleration functions. This has a bunch of drawbacks, not
least that we already have to un-normalize back into device units for a few
devices already (trackpoints, tablet, low-dpi mice).
Switch the filter code over to use device units, relying on the dpi set
earlier during filter creation to convert to normalized. To make things easy,
the output of the filter code is still normalized data, i.e. data ready to be
handed to the libinput caller.
No effective functional changes. For touchpads, we still send normalized
coordinates (for now, anyway). For the various filter methods, we either drop
the places where we unnormalized before or we normalize where needed.
Two possible changes: for trackpoints and low-dpi mice we had a max dpi factor
of 1.0 before - now we don't anymore. This was only the case if a low-dpi
mouse had more than 1000dpi (never true) or a trackpoint had a const accel
lower than 1.0 (yeah, whatever).
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2016-12-15 08:36:22 +10:00
|
|
|
* @param filter The device's motion filter
|
|
|
|
|
* @param unaccelerated The unaccelerated delta in the device's dpi
|
|
|
|
|
* resolution as specified during filter creation. If a device has uneven
|
|
|
|
|
* resolution for x and y, one axis needs to be scaled to match the
|
|
|
|
|
* originally provided resolution.
|
|
|
|
|
* @param data Custom data
|
|
|
|
|
* @param time The time of the delta
|
|
|
|
|
*
|
|
|
|
|
* @return A set of normalized coordinates that can be used for pixel
|
2020-08-27 19:52:34 +02:00
|
|
|
* movement. The normalized coordinates are scaled to the default dpi range,
|
filter: change the filter functions to take raw device coordinates
We used to normalize all deltas to equivalents of a 1000dpi mouse before
passing it into the acceleration functions. This has a bunch of drawbacks, not
least that we already have to un-normalize back into device units for a few
devices already (trackpoints, tablet, low-dpi mice).
Switch the filter code over to use device units, relying on the dpi set
earlier during filter creation to convert to normalized. To make things easy,
the output of the filter code is still normalized data, i.e. data ready to be
handed to the libinput caller.
No effective functional changes. For touchpads, we still send normalized
coordinates (for now, anyway). For the various filter methods, we either drop
the places where we unnormalized before or we normalize where needed.
Two possible changes: for trackpoints and low-dpi mice we had a max dpi factor
of 1.0 before - now we don't anymore. This was only the case if a low-dpi
mouse had more than 1000dpi (never true) or a trackpoint had a const accel
lower than 1.0 (yeah, whatever).
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2016-12-15 08:36:22 +10:00
|
|
|
* i.e. regardless of the resolution of the underlying device, the returned
|
|
|
|
|
* values always reflect a 1000dpi mouse.
|
|
|
|
|
*
|
2015-08-17 16:32:20 +10:00
|
|
|
* @see filter_dispatch_constant
|
|
|
|
|
*/
|
2015-03-19 11:02:51 +10:00
|
|
|
struct normalized_coords
|
2013-11-10 17:55:40 +01:00
|
|
|
filter_dispatch(struct motion_filter *filter,
|
filter: change the filter functions to take raw device coordinates
We used to normalize all deltas to equivalents of a 1000dpi mouse before
passing it into the acceleration functions. This has a bunch of drawbacks, not
least that we already have to un-normalize back into device units for a few
devices already (trackpoints, tablet, low-dpi mice).
Switch the filter code over to use device units, relying on the dpi set
earlier during filter creation to convert to normalized. To make things easy,
the output of the filter code is still normalized data, i.e. data ready to be
handed to the libinput caller.
No effective functional changes. For touchpads, we still send normalized
coordinates (for now, anyway). For the various filter methods, we either drop
the places where we unnormalized before or we normalize where needed.
Two possible changes: for trackpoints and low-dpi mice we had a max dpi factor
of 1.0 before - now we don't anymore. This was only the case if a low-dpi
mouse had more than 1000dpi (never true) or a trackpoint had a const accel
lower than 1.0 (yeah, whatever).
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2016-12-15 08:36:22 +10:00
|
|
|
const struct device_float_coords *unaccelerated,
|
2025-07-01 16:30:11 +10:00
|
|
|
void *data,
|
|
|
|
|
uint64_t time);
|
2015-06-10 09:54:06 +10:00
|
|
|
|
2015-08-17 16:32:20 +10:00
|
|
|
/**
|
|
|
|
|
* Apply constant motion filters, but no acceleration.
|
|
|
|
|
*
|
|
|
|
|
* Takes a set of unaccelerated deltas and applies any constant filters to
|
|
|
|
|
* it but does not accelerate the delta in the conventional sense.
|
|
|
|
|
*
|
filter: change the filter functions to take raw device coordinates
We used to normalize all deltas to equivalents of a 1000dpi mouse before
passing it into the acceleration functions. This has a bunch of drawbacks, not
least that we already have to un-normalize back into device units for a few
devices already (trackpoints, tablet, low-dpi mice).
Switch the filter code over to use device units, relying on the dpi set
earlier during filter creation to convert to normalized. To make things easy,
the output of the filter code is still normalized data, i.e. data ready to be
handed to the libinput caller.
No effective functional changes. For touchpads, we still send normalized
coordinates (for now, anyway). For the various filter methods, we either drop
the places where we unnormalized before or we normalize where needed.
Two possible changes: for trackpoints and low-dpi mice we had a max dpi factor
of 1.0 before - now we don't anymore. This was only the case if a low-dpi
mouse had more than 1000dpi (never true) or a trackpoint had a const accel
lower than 1.0 (yeah, whatever).
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2016-12-15 08:36:22 +10:00
|
|
|
* @param filter The device's motion filter
|
|
|
|
|
* @param unaccelerated The unaccelerated delta in the device's dpi
|
|
|
|
|
* resolution as specified during filter creation. If a device has uneven
|
|
|
|
|
* resolution for x and y, one axis needs to be scaled to match the
|
|
|
|
|
* originally provided resolution.
|
|
|
|
|
* @param data Custom data
|
|
|
|
|
* @param time The time of the delta
|
|
|
|
|
*
|
2015-08-17 16:32:20 +10:00
|
|
|
* @see filter_dispatch
|
|
|
|
|
*/
|
|
|
|
|
struct normalized_coords
|
|
|
|
|
filter_dispatch_constant(struct motion_filter *filter,
|
filter: change the filter functions to take raw device coordinates
We used to normalize all deltas to equivalents of a 1000dpi mouse before
passing it into the acceleration functions. This has a bunch of drawbacks, not
least that we already have to un-normalize back into device units for a few
devices already (trackpoints, tablet, low-dpi mice).
Switch the filter code over to use device units, relying on the dpi set
earlier during filter creation to convert to normalized. To make things easy,
the output of the filter code is still normalized data, i.e. data ready to be
handed to the libinput caller.
No effective functional changes. For touchpads, we still send normalized
coordinates (for now, anyway). For the various filter methods, we either drop
the places where we unnormalized before or we normalize where needed.
Two possible changes: for trackpoints and low-dpi mice we had a max dpi factor
of 1.0 before - now we don't anymore. This was only the case if a low-dpi
mouse had more than 1000dpi (never true) or a trackpoint had a const accel
lower than 1.0 (yeah, whatever).
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2016-12-15 08:36:22 +10:00
|
|
|
const struct device_float_coords *unaccelerated,
|
2025-07-01 16:30:11 +10:00
|
|
|
void *data,
|
|
|
|
|
uint64_t time);
|
2015-08-17 16:32:20 +10:00
|
|
|
|
2023-02-18 21:12:13 +02:00
|
|
|
/**
|
|
|
|
|
* Apply a scroll filter.
|
|
|
|
|
* Depending on the device, and the acceleration profile,
|
|
|
|
|
* this filter allows the user to accelerate the scroll movement.
|
|
|
|
|
*
|
|
|
|
|
* Takes a set of unaccelerated deltas and applies the scroll filter to it.
|
|
|
|
|
*
|
|
|
|
|
* @param filter The device's motion filter
|
|
|
|
|
* @param unaccelerated The unaccelerated delta in the device's dpi
|
|
|
|
|
* resolution as specified during filter creation. If a device has uneven
|
|
|
|
|
* resolution for x and y, one axis needs to be scaled to match the
|
|
|
|
|
* originally provided resolution.
|
|
|
|
|
* @param data Custom data
|
|
|
|
|
* @param time The time of the delta
|
|
|
|
|
*
|
|
|
|
|
* @see filter_dispatch
|
|
|
|
|
*/
|
|
|
|
|
struct normalized_coords
|
|
|
|
|
filter_dispatch_scroll(struct motion_filter *filter,
|
|
|
|
|
const struct device_float_coords *unaccelerated,
|
2025-07-01 16:30:11 +10:00
|
|
|
void *data,
|
|
|
|
|
uint64_t time);
|
2023-02-18 21:12:13 +02:00
|
|
|
|
2015-06-10 09:54:06 +10:00
|
|
|
void
|
2025-07-01 16:30:11 +10:00
|
|
|
filter_restart(struct motion_filter *filter, void *data, uint64_t time);
|
2015-06-10 09:54:06 +10:00
|
|
|
|
2014-07-04 09:39:05 +10:00
|
|
|
void
|
|
|
|
|
filter_destroy(struct motion_filter *filter);
|
2012-05-17 12:18:17 +02:00
|
|
|
|
2014-07-03 15:53:56 +10:00
|
|
|
bool
|
2025-07-01 16:30:11 +10:00
|
|
|
filter_set_speed(struct motion_filter *filter, double speed);
|
2014-07-03 15:53:56 +10:00
|
|
|
double
|
|
|
|
|
filter_get_speed(struct motion_filter *filter);
|
|
|
|
|
|
2015-08-27 13:13:47 +10:00
|
|
|
enum libinput_config_accel_profile
|
|
|
|
|
filter_get_type(struct motion_filter *filter);
|
|
|
|
|
|
2013-11-10 17:55:40 +01:00
|
|
|
typedef double (*accel_profile_func_t)(struct motion_filter *filter,
|
2012-05-17 12:18:17 +02:00
|
|
|
void *data,
|
|
|
|
|
double velocity,
|
2014-04-08 12:29:45 +02:00
|
|
|
uint64_t time);
|
2012-05-17 12:18:17 +02:00
|
|
|
|
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
|
|
|
bool
|
|
|
|
|
filter_set_accel_config(struct motion_filter *filter,
|
2025-07-01 16:30:11 +10:00
|
|
|
struct libinput_config_accel *accel_config);
|
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
|
|
|
|
2015-07-28 15:06:13 +10:00
|
|
|
/* Pointer acceleration types */
|
2015-08-27 13:13:47 +10:00
|
|
|
struct motion_filter *
|
|
|
|
|
create_pointer_accelerator_filter_flat(int dpi);
|
2015-07-28 15:06:13 +10:00
|
|
|
|
|
|
|
|
struct motion_filter *
|
2018-08-17 15:12:58 +02:00
|
|
|
create_pointer_accelerator_filter_linear(int dpi, bool use_velocity_averaging);
|
2015-07-28 15:06:13 +10:00
|
|
|
|
|
|
|
|
struct motion_filter *
|
2018-08-17 15:12:58 +02:00
|
|
|
create_pointer_accelerator_filter_linear_low_dpi(int dpi, bool use_velocity_averaging);
|
2015-07-28 15:06:13 +10:00
|
|
|
|
|
|
|
|
struct motion_filter *
|
2017-07-02 16:35:36 +02:00
|
|
|
create_pointer_accelerator_filter_touchpad(int dpi,
|
2025-07-01 16:30:11 +10:00
|
|
|
uint64_t event_delta_smooth_threshold,
|
|
|
|
|
uint64_t event_delta_smooth_value,
|
|
|
|
|
bool use_velocity_averaging);
|
2015-07-28 15:06:13 +10:00
|
|
|
|
2020-05-22 13:24:34 -04:00
|
|
|
struct motion_filter *
|
|
|
|
|
create_pointer_accelerator_filter_touchpad_flat(int dpi);
|
|
|
|
|
|
2013-11-10 17:55:40 +01:00
|
|
|
struct motion_filter *
|
2018-08-17 15:12:58 +02:00
|
|
|
create_pointer_accelerator_filter_lenovo_x230(int dpi, bool use_velocity_averaging);
|
2012-05-17 12:18:17 +02:00
|
|
|
|
2015-07-28 16:02:05 +10:00
|
|
|
struct motion_filter *
|
2025-07-01 16:30:11 +10:00
|
|
|
create_pointer_accelerator_filter_trackpoint(double multiplier,
|
|
|
|
|
bool use_velocity_averaging);
|
2015-07-28 16:02:05 +10:00
|
|
|
|
2022-09-05 11:33:57 +10:00
|
|
|
struct motion_filter *
|
|
|
|
|
create_pointer_accelerator_filter_trackpoint_flat(double multiplier);
|
|
|
|
|
|
2016-01-06 15:26:49 +10:00
|
|
|
struct motion_filter *
|
|
|
|
|
create_pointer_accelerator_filter_tablet(int xres, int yres);
|
|
|
|
|
|
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
|
|
|
struct motion_filter *
|
|
|
|
|
create_custom_accelerator_filter(void);
|
|
|
|
|
|
2014-05-18 19:20:39 +02:00
|
|
|
/*
|
|
|
|
|
* Pointer acceleration profiles.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
double
|
2015-06-23 12:45:16 +10:00
|
|
|
pointer_accel_profile_linear_low_dpi(struct motion_filter *filter,
|
|
|
|
|
void *data,
|
|
|
|
|
double speed_in,
|
|
|
|
|
uint64_t time);
|
|
|
|
|
double
|
2014-09-19 11:10:17 +10:00
|
|
|
pointer_accel_profile_linear(struct motion_filter *filter,
|
|
|
|
|
void *data,
|
|
|
|
|
double speed_in,
|
|
|
|
|
uint64_t time);
|
2015-03-13 13:56:14 +10:00
|
|
|
double
|
|
|
|
|
touchpad_accel_profile_linear(struct motion_filter *filter,
|
|
|
|
|
void *data,
|
|
|
|
|
double speed_in,
|
|
|
|
|
uint64_t time);
|
2015-04-23 14:32:40 -04:00
|
|
|
double
|
|
|
|
|
touchpad_lenovo_x230_accel_profile(struct motion_filter *filter,
|
2025-07-01 16:30:11 +10:00
|
|
|
void *data,
|
|
|
|
|
double speed_in,
|
|
|
|
|
uint64_t time);
|
2015-07-28 16:02:05 +10:00
|
|
|
double
|
|
|
|
|
trackpoint_accel_profile(struct motion_filter *filter,
|
|
|
|
|
void *data,
|
2020-08-27 01:00:31 -07:00
|
|
|
double velocity,
|
2018-06-27 15:53:23 +10:00
|
|
|
uint64_t time);
|
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
|
|
|
double
|
|
|
|
|
custom_accel_profile_fallback(struct motion_filter *filter,
|
|
|
|
|
void *data,
|
|
|
|
|
double speed_in,
|
|
|
|
|
uint64_t time);
|
|
|
|
|
double
|
|
|
|
|
custom_accel_profile_motion(struct motion_filter *filter,
|
|
|
|
|
void *data,
|
|
|
|
|
double speed_in,
|
|
|
|
|
uint64_t time);
|
2023-02-18 21:12:13 +02:00
|
|
|
double
|
|
|
|
|
custom_accel_profile_scroll(struct motion_filter *filter,
|
|
|
|
|
void *data,
|
|
|
|
|
double speed_in,
|
|
|
|
|
uint64_t time);
|
2013-11-10 17:55:40 +01:00
|
|
|
#endif /* FILTER_H */
|