[PATCH weston v3 0/5] improving support for systems without a pointer device

This is v2 patch rebased against master. I've tested it on my systems, seems ok. The only thing I find strange is exposay animation, it looks like zoom in/out is reversed, but that happens without this patch as well, also, this happened with weston 1.4 Stanislav Vorobiov (5): shell: support wind

[PATCH weston v3 5/5] shared/frame: fix frame buttons for touchscreen

support frame buttons hovering with touchscreen and cancel button press if a touch was not released over the button that was pressed --- clients/window.c| 14 ++ shared/cairo-util.h |3 +++ shared/frame.c | 44 ++-- 3 files chang

[PATCH weston v3 2/5] shell: support zooming without a pointer device

if the system doesn't have a pointer device do_zoom will crash on accessing seat->pointer->x. here we implement zoom support on systems with a touchscreen, touchscreen's last touch point is simply used instead of pointer's current position --- desktop-shell/shell.c | 22 -- s

[PATCH weston v3 4/5] exposay: support systems without a pointer device

if the system doesn't have a pointer device exposay_transition_active will crash in weston_pointer_start_grab(seat->pointer, ...). here we fix that and also implement exposay support on systems with a touchscreen --- desktop-shell/exposay.c | 95 --- d

[PATCH weston v3 3/5] data-device: fix crash on systems with no pointer device

--- src/data-device.c | 19 +-- 1 file changed, 13 insertions(+), 6 deletions(-) diff --git a/src/data-device.c b/src/data-device.c index 6a81bc8..abab735 100644 --- a/src/data-device.c +++ b/src/data-device.c @@ -421,6 +421,7 @@ static void drag_grab_touch_down(struct weston_t

[PATCH weston v3 1/5] shell: support window resizing using touchscreen

if the system doesn't have a pointer device common_surface_resize will crash on accessing seat->pointer->button_count. if the system does have a pointer device, but attempts to resize a window using touchscreen - nothing happens. here we implement separate window resizing path for seat->touch as it

Change bg image in default weston.ini

The weston.ini included in weston names a background image file that does not exist on all machines, and produces a pretty ugly blue result. I would recommend that all the background- lines be commented out so you get the default tiled doily pattern on all systems.

Re: [PATCH 1/2] cairo-util: Add frame_touch_motion support

On Tue, May 13, 2014 at 5:46 AM, Stanislav Vorobiov wrote: > Hi, > > Recently I've sent patches to ML that implement just that, see - > http://lists.freedesktop.org/archives/wayland-devel/2014-May/014602.html > I got no comments on them though... > Yes, these kind of have to be developed side-by-

Config bug in wayland

Trying to replicate my success at building Wayland, starting from scratch, I found an error at the first step if $ALOCAL is exported as stated, and no install has ever been done: ~/Wayland/wayland$ ./autogen.sh --prefix=$WLD autoreconf: Entering directory `.' autoreconf: configure.ac: not using

[PATCH 0/2] clients: Fix race conditions.

While experimenting by writing a protocol dumper which acts as a proxy between clients and weston, I've noticed that all clients using toytoolkit and simple-touch were crashing or failing. It is due to the proxy slowing the packets, which causes some races in the clients. The following patches ad

[PATCH 2/2] window: Make a roundtrip to ensure globals have been enumerated.

If the compositor enumerates the globals too slowly, the d->sum pointer is still NULL by the time create_cursors is called, and leads to a null pointer dereferencing. A roundtrip is needed to make sure all globals have been enumerated. Signed-off-by: Paul Liétar --- clients/window.c | 6 +-

Re: Not able to build weston following the instructions in the website.

I was hoping to clean this up, but I thought I would post my current notes on getting Wayland compiled, on an Ubuntu 12.04 machine. This machine had been used to compile X11 programs, thus it may have packages already installed that are required for Wayland. I did start with http://wayland.fre

RE: Not able to build weston following the instructions in the website.

> -Original Message- > From: wayland-devel [mailto:wayland-devel- > boun...@lists.freedesktop.org] On Behalf Of Pekka Paalanen > Sent: Tuesday, May 13, 2014 1:03 PM > To: Srivardhan > Cc: wayland-devel@lists.freedesktop.org > Subject: Re: Not able to build weston following the instruction

Re: [PATCH 1/2] cairo-util: Add frame_touch_motion support

Hi, Recently I've sent patches to ML that implement just that, see - http://lists.freedesktop.org/archives/wayland-devel/2014-May/014602.html I got no comments on them though... On 05/13/2014 02:14 PM, Boyan Ding wrote: > Hi Jason, > > In writing v2 of the patches I found out frame_touch_motion

Re: [PATCH 1/2] cairo-util: Add frame_touch_motion support

Hi Jason, In writing v2 of the patches I found out frame_touch_motion isn't that easy as it seems. For there's something tricky. Without frame_touch_motion the code actually works all right - finger down on a button presses the button and finger up releases it, regardless of where the finger has

Re: Not able to build weston following the instructions in the website.

On Tue, 13 May 2014 12:44:45 +0530 Srivardhan wrote: > Hi, > > When followed the instructions in the > http://wayland.freedesktop.org/building.html, Weston configure fails, as it > won't find the wayland-scanner installed in custom location. So we need to > update the build instructions in the w

Not able to build weston following the instructions in the website.

Hi, When followed the instructions in the http://wayland.freedesktop.org/building.html, Weston configure fails, as it won't find the wayland-scanner installed in custom location. So we need to update the build instructions in the website to update the PATH variable with custom location. Has nobody

A newbie task: [Bug 78585] multiple monitor fullscreen images incorrect position/scale

Hi all, there have recently been many questions about where to start learning or hacking Wayland. Here is one suggestion. The bug referred below is about some misbehaviour with fullscreening an SDL2 game under Weston. If you want to dive into Wayland and Weston, you could: - try to reproduce the