On Thu, Jul 25, 2013 at 6:51 AM, Jiergir Ogoerg wrote:
> Hi,
> I think in wayland-client.c the function
> wl_display_dispatch_queue_pending(...)
> could be simplified
> from this:
> pthread_mutex_lock(&display->mutex);
> if (dispatch_queue(display, queue) == -1)
> goto err_unlock;
Hi,
I think in wayland-client.c the function
wl_display_dispatch_queue_pending(...)
could be simplified
from this:
pthread_mutex_lock(&display->mutex);
if (dispatch_queue(display, queue) == -1)
goto err_unlock;
pthread_mutex_unlock(&display->mutex);
return 0;
err_unlock:
Hi,
On 22 July 2013 17:31, Rob Bradford wrote:
> The Wayland protocol permits a client to request the pointer, keyboard
> and touch multiple times from the seat global. This is very useful in a
> component like Clutter-GTK where we are combining two libraries that use
> Wayland together.
>
> This
Yep, makes a lot of sense - it was only in there originally due to the
libwayland-server/weston input split.
On 22 July 2013 17:31, Rob Bradford wrote:
> From: Rob Bradford
>
> This removes the use of wl_client_get_display() where the client is
> derived from the focussed resource. This starts t
The eagle eyed amongst you will notice these are patches for weston..whoops :-)
Rob
On 24 July 2013 16:57, Rob Bradford wrote:
> From: Rob Bradford
>
> Prior to freeing the memory in which the link node for the signal is
> emedded we should remove the link node from the list to prevent the list
From: Rob Bradford
Prior to freeing the memory in which the link node for the signal is
emedded we should remove the link node from the list to prevent the list
from being corrupted.
https://bugs.freedesktop.org/show_bug.cgi?id=67231
---
src/clipboard.c | 1 +
1 file changed, 1 insertion(+)
di
From: Rob Bradford
Prior to freeing the memory in which the link node for the signal is
emedded we should remove the link node from the list to prevent the list
from being corrupted.
https://bugs.freedesktop.org/show_bug.cgi?id=67231
---
src/text-backend.c | 1 +
1 file changed, 1 insertion(+)
