A generic interface for devices that provide buttons and axes, but don't
control the pointer. This caters for the Pad part of Wacom graphics tablets
but could eventually also deal with remote controls, 3D mice and other
devices.
This patch adds a new interface "buttonset" with a new capability and
From: Benjamin Tissoires
Same approach as evdev-tablet (started as copy/paste), with axis and buttons
adjusted. Wacom's handling of pad devices requires a lot of non-obvious
handling, e.g. ABS_THROTTLE is the second ring, ABS_RX is the strip, etc.
This is not generic buttonset code, if we start
This is a re-vamped version of the buttonset interface. Still WIP but I'd
like to get some comments on the API.
Changes to the last version:
This version now uses numbered axes instead of typed axes. Previously the
interface used a unique axis type to deal with axes (e.g.
LIBINPUT_BUTTONSET_AXIS_
---
cursor/wayland-cursor.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/cursor/wayland-cursor.c b/cursor/wayland-cursor.c
index 1a5393a..410a0d4 100644
--- a/cursor/wayland-cursor.c
+++ b/cursor/wayland-cursor.c
@@ -190,6 +190,7 @@ wl_cursor_destroy(struct wl_cursor *cursor)
for (i
Replaced by gdk_cursor_new_from_display() which means we need to tickle the
event until it spits out a GdkDisplay.
Deprecated in gdk 3.16
Signed-off-by: Peter Hutterer
---
If anyone can do a quick double-check that I'm not mis-using gdk here please
that'd be appreciated.
tools/event-gui.c | 8
Signed-off-by: Bryce Harrington
---
src/wayland-client.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/wayland-client.c b/src/wayland-client.c
index 0f1405c..9adde38 100644
--- a/src/wayland-client.c
+++ b/src/wayland-client.c
@@ -955,7 +955,7 @@ static const struct wl_c
On 17/03/15 07:34 AM, Pekka Paalanen wrote:
> On Tue, 17 Mar 2015 13:02:34 +0100
> Thilo Cestonaro wrote:
>
>> Hey!
>>
>>> Just curious, why didn't you get the fbdev backend to work? Was it the
>>> color format thing?
>>>
>> No, I got the color format to work, but I need to rotate the screen, and
Signed-off-by: Derek Foreman
---
src/compositor-fbdev.c | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/src/compositor-fbdev.c b/src/compositor-fbdev.c
index ae526e5..c08f170 100644
--- a/src/compositor-fbdev.c
+++ b/src/compositor-fbdev.c
@@ -503,11 +503,14 @@
The pixman-renderer is already performing transformations when compositing
into the shadow buffer, we just need to get the damage co-ordinates right
when copying from shadow to front.
Signed-off-by: Derek Foreman
---
src/compositor-fbdev.c | 110 +
Signed-off-by: Derek Foreman
---
src/compositor-rpi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/compositor-rpi.c b/src/compositor-rpi.c
index 2d72686..bceb280 100644
--- a/src/compositor-rpi.c
+++ b/src/compositor-rpi.c
@@ -344,6 +344,7 @@ rpi_output_create(struct rpi_compositor *co
If you have devices configured in seats with udev then the output names
are tested with string compare. This fixes a potential crash on startup and
device insertion.
Signed-off-by: Derek Foreman
---
src/compositor-fbdev.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/compositor-fbdev.
fbdev transforms are currently broken, and can only be enabled by changing
code. This series enables it in the config file (after adding an output
name so it can be specified there).
There's also some other output name stuff in here as well. I have a second
keyboard and mouse configured on a dif
If an output is unnamed and devices are in seats, the strcmp will crash.
Signed-off-by: Derek Foreman
---
src/libinput-seat.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/libinput-seat.c b/src/libinput-seat.c
index ef2d804..c0a87ea 100644
--- a/src/libinput-seat.c
++
Hi,
On 17-03-15 06:35, Peter Hutterer wrote:
On Mon, Mar 16, 2015 at 02:58:02PM +0100, Hans de Goede wrote:
Hi,
On 12-03-15 09:23, Peter Hutterer wrote:
On Wed, Mar 11, 2015 at 03:20:55PM +0100, Hans de Goede wrote:
Implement touchpad pinch (and rotate) gesture support.
WIP: TODO: fix tests
On Mar 17, 2015 5:34 AM, "Pekka Paalanen" wrote:
>
> On Tue, 17 Mar 2015 13:02:34 +0100
> Thilo Cestonaro wrote:
>
> > Hey!
> >
> > > Just curious, why didn't you get the fbdev backend to work? Was it the
> > > color format thing?
> > >
> > No, I got the color format to work, but I need to rotate
On Tue, 17 Mar 2015 13:02:34 +0100
Thilo Cestonaro wrote:
> Hey!
>
> > Just curious, why didn't you get the fbdev backend to work? Was it the
> > color format thing?
> >
> No, I got the color format to work, but I need to rotate the screen, and
> the rotation in fbdev doesn't work as expected.
Hey!
Just curious, why didn't you get the fbdev backend to work? Was it the
color format thing?
No, I got the color format to work, but I need to rotate the screen, and
the rotation in fbdev doesn't work as expected.
(I changed compositor-fbdev.c - weston_output_init() or so, to have the
Tran
On Tue, 17 Mar 2015 11:20:57 +0100
Thilo Cestonaro wrote:
> Hey!
>
> Weston runs! And rotated! Altough not with fbdev-compositor :) but with
> drm and pixman.
DRM-backend is the way to go indeed, it is strictly superior to the
fbdev-backend.
Just curious, why didn't you get the fbdev backend
Hi,
On 17-03-15 06:34, Peter Hutterer wrote:
The struct evdev_device's absinfo_x/y point to the right axis
Signed-off-by: Peter Hutterer
The entire series looks good to me and is:
Reviewed-by: Hans de Goede
Regards,
Hans
---
src/evdev-mt-touchpad.c | 13 ++---
1 file changed
Hey!
Weston runs! And rotated! Altough not with fbdev-compositor :) but with
drm and pixman.
As weston now runs, I have different questions.
The first is: I want to run exactly one App in Weston, no Desktop, no
Panel ... just that one App in Fullscreen mode.
Is the fullscreen-shell for thi
On Fri, 13 Mar 2015 12:30:15 +0200
Pekka Paalanen wrote:
> > on Monday 09 March 2015 08:59:35,Jasper St. Pierre wrote:
> > > You misunderstood what pq said.
> > >
> > > You work in "logical pixels". On a hi-DPI display, with twice the pixel
> > > density, each "logical pixel" is backed by 4 devi
21 matches
Mail list logo