Re: [RFC wayland] doc: generate doxygen html output from the scanner

On Sat, 7 Nov 2015 09:53:10 +1000 Peter Hutterer wrote: > On 7/11/2015 01:27 , Pekka Paalanen wrote: > > On Thu, 29 Oct 2015 11:48:01 +1000 > > Peter Hutterer wrote: > > > >> This switches the scanner to generate doxygen-compatible tags for the > >> generated protocol headers, and hooks up the d

[PATCH libinput] touchpad: reduced the 2fg scroll threshold to 1mm

At least on the t440, this is enough to trigger correct detection between swipe and scroll 90% of the time. Since scrolling is significantly more prevalent than gesturing, erring on the side of scrolling at the cost of misdetecting some gestures is acceptable. Signed-off-by: Peter Hutterer --- s

[PATCH wayland 0/3] Restore DTD and use wayland-scanner to validate

This patchset restores the dtd (and adds a new element "description" to the tag) and adds the validation bits. Since expat doesn't validate, a second library is used (libxml2). To avoid breakage, it's hooked up independently of the current parser, so we essentially just parse the input twice, spi

[PATCH wayland 1/3] Revert "Remove protocol/wayland.dtd"

This reverts commit 06fb8bd371403d43bc192577abd6b0a0c8b29c59. Having a DTD hooked up gives an indication of what we expect the protocol to be, which is a clearer documentation than the current "whatever scanner.c manages to parse". Signed-off-by: Peter Hutterer --- Makefile.am | 4 ++-

[PATCH wayland 3/3] Validate the protocol xml during scanning

Embed the wayland.dtd protocol data into the scanner binary so we can validate external protocol files without requiring makefile changes. Hat-tip to Pekka Paalanen for the embedding trick. The embedding trick doesn't work well if the to-be-embedded file is in a different location than the source f

[PATCH wayland 2/3] protocol: allow for a element below

The scanner parses this already, it doesn't do anything with it though. The DTD requires the order to be copyright, description, then the interfaces. That's largely a DTD limitation, the scanner doesn't care. Signed-off-by: Peter Hutterer --- protocol/wayland.dtd | 2 +- 1 file changed, 1 inser

[PATCH wayland-protocols] xdg_shell: add missing tags to the 'state' enum entries

The scanner parses CDATA in but lets it disappear otherwise. To have descriptive text associated with the , we need a tag - and that must have a summary attribute. The current scanner doesn't handle however, so to get the summary printed in the output file we still need the summary attribute in

Re: [PATCH libinput] Documentation fixes to arrows in svg files

On Sat, Nov 07, 2015 at 10:34:03PM +0200, Tomi Leppänen wrote: > 17.09.2015, 21:56, Bryce Harrington kirjoitti: > >On Thu, Sep 17, 2015 at 03:05:25PM +0300, Tomi Leppänen wrote: > >>There were two files (doc/svg/{edge,twofinger}-scrolling.svg) that had both > >>arrow heads pointing to wrong directi

Re: ThinkPad twist: disable trackpoint and touchpad when closed

On Fri, Nov 06, 2015 at 10:01:39PM +0100, Ruben De Smet wrote: > With respect to > http://lists.freedesktop.org/archives/wayland-devel/2014-September/017259.html > and https://bugzilla.gnome.org/show_bug.cgi?id=698226: > > I own a ThinkPad Twist, which has a tablet mode. When in tablet mode, > the

Re: Xwayland and weston’s scale=2 (hi-dpi display)

On Sat, Nov 07, 2015 at 09:48:59PM +0100, Michael Stapelberg wrote: > Hey, > > I just got around to trying Wayland on my ThinkPad X1 Carbon 2015. > > The machine has a 2560x1440px display with 220 DPI, hence I’m using it as a > “retina display”, i.e. with a scale factor of 2. On Xorg, I achieve t

Re: libinput and scrolling threshold/deadspot

On Fri, Nov 06, 2015 at 01:31:06PM +0100, Mads wrote: > Hi! > > Using xf86-input-libinput 0.15.0 and libinput 1.1.0, are there any way to > tweak the size of the scrolling deadspot? That is, how many pixels of > movement libinput ignores before starting a scroll event (e.g. two fingers > vertical