Re: [PATCH libinput 1/2] Change the scroll step distance to 15 and document it as degrees

On Mon, Jan 12, 2015 at 09:37:05AM +0800, Jonas Ådahl wrote: > On Mon, Jan 12, 2015 at 09:12:35AM +1000, Peter Hutterer wrote: > > Similar to the mouse resolution, let's make the scroll distance a sensible > > predictable value. Most mice use a 15 degree angle per scroll click, so > > let's > > ch

Re: [PATCH v2 libinput] Change axis events to carry all directions

On Fri, Jan 09, 2015 at 01:05:53PM +0100, Hans de Goede wrote: > Hi, > > On 07-01-15 02:33, Peter Hutterer wrote: > >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 s

Re: [PATCH libinput 2/2] Parse the MOUSE_WHEEL_CLICK_ANGLE udev property if present

On Mon, Jan 12, 2015 at 09:12:36AM +1000, Peter Hutterer wrote: > Signed-off-by: Peter Hutterer Reviewed-by: Jonas Ådahl > --- > doc/device-configuration-via-udev.dox | 4 > src/evdev.c | 29 +++-- > src/evdev.h

Re: [PATCH libinput 1/2] Change the scroll step distance to 15 and document it as degrees

On Mon, Jan 12, 2015 at 09:12:35AM +1000, Peter Hutterer wrote: > Similar to the mouse resolution, let's make the scroll distance a sensible > predictable value. Most mice use a 15 degree angle per scroll click, so let's > change to that. This will alter behaviour in clients that expect 10 but it >

Re: [PATCH weston] Fix "Back", "Forward", and other special mouse buttons in the X11 compositor.

Looks like this patch got discarded (according to patchwork)? This one is different from http://patchwork.freedesktop.org/patch/39499/. That one fixed the Wayland->X11 key code translation; this one fixes X11->Wayland. On Dec 22, 2014 11:51 AM, "Dima Ryazanov" wrote: > They're off by 4 because o

Re: [PATCH v1] Added touch support to wayland backend

On Wed, Dec 17, 2014 at 04:11:56PM +0200, Imran Zaman wrote: > Nested westons (with wayland backend as child weston) is one possible > use case for the needed touch support. > > Signed-off-by: Imran Zaman Have a look at these patches: http://lists.freedesktop.org/archives/wayland-devel/2014-May/

[PATCH libinput 2/2] Parse the MOUSE_WHEEL_CLICK_ANGLE udev property if present

Signed-off-by: Peter Hutterer --- doc/device-configuration-via-udev.dox | 4 src/evdev.c | 29 +++-- src/evdev.h | 3 +++ src/libinput-util.c | 30 ++ src/libinput-util

[PATCH libinput 1/2] Change the scroll step distance to 15 and document it as degrees

Similar to the mouse resolution, let's make the scroll distance a sensible predictable value. Most mice use a 15 degree angle per scroll click, so let's change to that. This will alter behaviour in clients that expect 10 but it shouldn't be too bad. We return doubles anyway for the axis value, so t

wl_test / accessibility

Hi, I was curious whether wl_test (from weston) is intended to eventually be moved into wayland. I'm asking because it contains functionality (such as being able to track and move the mouse pointer) that the Orca screen reader relies on[1], so I'm trying to decide whether it makes sense to us

Re: [PATCH libinput] build-pedantic: use main(void)

On Fri, Jan 09, 2015 at 10:34:46AM +0100, Marek Chalupa wrote: > Main has unused parameters argc and argv. Since they are unused and > C 99 allows to prototype main as 'int main(void)', > remove them and replace by void. It fixes build when unused parameters > are treated as errors. > > Signed-off

Re: [PATCH weston v2 2/2] releasing: Add example commands to release directions

On Fri, Jan 09, 2015 at 06:09:21PM -0800, Bryce Harrington wrote: > Note that for weston, configure.ac needs version numbers updated in > several places. `make distcheck` for weston no longer triggers the test > suite to run, so update the directions to run a `make check` > pre-release. Switch to

Re: [PATCH v2] xwm: tell the shell the pid of the X clients

2015-01-11 12:26 GMT+02:00 Giulio Camuffo : > 2015-01-11 10:33 GMT+02:00 Jasper St. Pierre : >> In the case of X clients, using XKillClient instead of killing the PID would >> be much nicer. >> >> On Sat, Jan 10, 2015 at 3:27 AM, Giulio Camuffo >> wrote: >>> >>> All the surfaces from all the X cli

[PATCH v3] xwm: tell the shell the pid of the X clients

All the surfaces from all the X clients share the same wl_client so wl_client_get_credentials can't be used to get the pid of the X clients. The shell may need to know the pid to be able to associate a surface with e.g. a DBus service. --- v3: added the implementation in shell.c desktop-shell/sh

Re: [weston1.5]Question about HardKey input monitor with wayland/weston

On Mon, 5 Jan 2015 11:48:00 + Yang Andy wrote: > Hi Pekka > > Thank you very much for your reply. > > > If you're interested in that, you can > >dig the wayland-devel mailing list archives, or if you can't find it, > >someone else probably can. This discussion was about any normal app > >th

Re: [PATCH v2] xwm: tell the shell the pid of the X clients

2015-01-11 10:33 GMT+02:00 Jasper St. Pierre : > In the case of X clients, using XKillClient instead of killing the PID would > be much nicer. > > On Sat, Jan 10, 2015 at 3:27 AM, Giulio Camuffo > wrote: >> >> All the surfaces from all the X clients share the same wl_client so >> wl_client_get_cre

Re: [PATCH v2] xwm: tell the shell the pid of the X clients

In the case of X clients, using XKillClient instead of killing the PID would be much nicer. On Sat, Jan 10, 2015 at 3:27 AM, Giulio Camuffo wrote: > All the surfaces from all the X clients share the same wl_client so > wl_client_get_credentials can't be used to get the pid of the X > clients. >

Re: wayland color depth 256 / 16 / 24 /32

On Wed, 7 Jan 2015 16:53:43 +0100 Damian Ivanov wrote: > Hi, > > What color depth works on wayland? Wayland does not really care. The actual compositors and clients would be the key here, and also the graphics driver implementations (EGL, GL, etc.) where acceleration is desired. If you need mo