Hey, look, almost year later and I found this email. In my defence, I was on
an airplane at the time, hence I missed this :)
This came up in #wayland where pekka linked to it, so I figured I might as
well look through it.
On Wed, Aug 16, 2017 at 09:19:06PM +0200, Quentin Glidic wrote:
> From: Que
libinput 1.10.4 is now available. Biggest user-noticeable change is that the
hysteresis threshold is significantly reduced to 0.25 of a mm now or to the
kernel fuzz value where present. This should make touchpads a bit more
snappy.
Two fixes for touchpad touch handling, one affecting semi-mt devic
On Fri, Mar 23, 2018 at 02:01:00PM +0200, Pekka Paalanen wrote:
> From: Louis-Francis Ratté-Boulianne
>
> In addition to the normal touch event processing mode, introduce a new
> mode for calibrating a touchscreen input device.
>
> In the calibration mode, normal touch event processing is skippe
On Fri, Mar 23, 2018 at 02:01:01PM +0200, Pekka Paalanen wrote:
> From: Pekka Paalanen
>
> This is a Wayland protocol extension to allow the calibration of
> touchscreens in Weston.
>
> See: https://phabricator.freedesktop.org/T7868
>
> Signed-off-by: Pekka Paalanen
> ---
> Makefile.am
On Fri, Mar 23, 2018 at 02:00:56PM +0200, Pekka Paalanen wrote:
> From: Pekka Paalanen
>
> notify_touch_cal() is an extended form of notify_touch(), adding
> normalized touch coordinates which are necessary for calibrating a
> touchscreen.
>
> It would be possible to invert the transformation an
On Fri, Mar 23, 2018 at 02:00:52PM +0200, Pekka Paalanen wrote:
> From: Louis-Francis Ratté-Boulianne
>
> Introduce weston_touch_device for libweston core to track individual
> touchscreen input devices. A weston_seat/weston_touch may be an
> aggregation of several physical touchscreen input devi
Signed-off-by: Drew DeVault
Reviewed-by: Simon Ser
---
Thanks Daniel for pointing out my silly mistakes
unstable/xdg-output/xdg-output-unstable-v1.xml | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/unstable/xdg-output/xdg-output-unstable-v1.xml
b/unstable/xd
On 2018-04-08 3:22 PM, Daniel Stone wrote:
> A name event would be great, but this is missing a string param to
> carry the actual name.
Whoops!
> In order to not breaking existing clients, it also needs to:
> - come after the 'done' event so we don't renumber events
> - bump the xdg_output
Hi all,
On 7 April 2018 at 19:01, Drew DeVault wrote:
> +
> +
> +Many compositors will assign names to their outputs, show them to the
> user,
> +allow them to be configured by name, etc. The client may wish to know
> this
> +name as well to offer the user similar behavior
