Add parsing for a LIBINPUT_ATTR_TRACKPOINT_RANGE property to enable
hardware-dependent ranges. These take precedence over the sensitivity parsing.
Signed-off-by: Peter Hutterer
---
src/evdev.c | 16
1 file changed, 16 insertions(+)
diff --git a/src/evdev.c b/src/evdev.c
index 9
This was to counteract hardware that doesn't work well out of the box,
resulting in quite different behavior across devices. Specifically, only
some trackpoints even have the sensitivity setting.
Change to take over all of the pointer acceleration on trackpoints, so we can
control the actual behav
Trackpoints can send very different ranges between the various pressures.
Collect the data and print it out to get an idea of what ranges are realistic.
Signed-off-by: Peter Hutterer
---
meson.build | 9 ++
tools/libinput-measure-trackpoint-range | 192 +
Switch to a pure factor with a max scaled after a function. The offset is just
0 now (will be removed eventually). Both are determined with a function based
on a linear/exponential regression of a sample set of data pairs.
Signed-off-by: Peter Hutterer
---
doc/pointer-acceleration.dox | 16 ++-
I've been working on this on and off for too long, it's time to get this
merged and adjusted later if need be.
Basic summary: we used to use the low-dpi acceleration method for
trackpoints, this patchset switches us to a basic linear acceleration
method. Many trackpoints have an acceleration func
>
> The idea is that having unmapped by null-attach means the
> xdg_surface/xdg_toplevel etc is reset to the exact same state that it
> had when first created, thus to map again, one would do what one would
> do the same as when mapping it for the first time: set up the state
> (set_title, (set_max
On Tue, Jul 11, 2017 at 11:30:11PM +0100, David Edmundson wrote:
> Can you clarify something here.
>
> >A newly-unmapped surface is considered to have met condition (1) out
> + of the 3 required conditions for mapping a surface if its role
> surface
> + has not been destroyed.
>
> Attac
Can you clarify something here.
>A newly-unmapped surface is considered to have met condition (1) out
+ of the 3 required conditions for mapping a surface if its role
surface
+ has not been destroyed.
Attaching a null buffer unmaps the surface
Unmapping the surface resets the state
The
wayland-protocols 1.8 has been available for some time wayland-protocols 1.9 is
now available.
Version 1.8 bumped the linux dmabuf protocol version, introducing a new request
for creating a buffer from a dmabuf without having to wait for an event, as
well as an event advertising supported fourcc m
On Fri, Jun 30, 2017 at 06:13:52PM +0200, Olivier Fourdan wrote:
> This adds a new protocol to let Wayland clients specify that they want
> all keyboard events to be sent to the client, regardless of the
> compositor own shortcuts.
>
> This protocol can be used for virtual machine and remote conne
On Fri, Jun 30, 2017 at 06:10:01PM +0200, Olivier Fourdan wrote:
> This patch introduces a new protocol for grabbing the keyboard from
> Xwayland.
>
> This is needed for X11 applications that map an override redirect window
> (thus not focused by the window manager) and issue an active grab on the
11 matches
Mail list logo
