Hi,
I checked e-mail before my leave to vacation and saw this message, so
here's a quick response:
The two questions answered Pekka (thanks).
More discussion about this pthread_cond broadcasting is here:
http://lists.freedesktop.org/archives/wayland-devel/2014-June/015632.html
http://lists.freed
On Tue, 22 Jul 2014 19:44:00 -0700
Jason Ekstrand wrote:
> Sorry for not looking at it. I'm mostly ok with the API so it's fine that
> you pushed it. I did have a question or two though.
>
>
> On Mon, Jul 7, 2014 at 7:28 AM, Pekka Paalanen wrote:
>
> > From: Marek Chalupa
> >
> > When an e
Sorry for not looking at it. I'm mostly ok with the API so it's fine that
you pushed it. I did have a question or two though.
On Mon, Jul 7, 2014 at 7:28 AM, Pekka Paalanen wrote:
> From: Marek Chalupa
>
> When an error occurs, wl_display_get_error() does not
> provide any way of getting kno
On Mon, 7 Jul 2014 17:41:25 +0300
Pekka Paalanen wrote:
> On Mon, 7 Jul 2014 17:28:11 +0300
> Pekka Paalanen wrote:
>
> > From: Marek Chalupa
> >
> > When an error occurs, wl_display_get_error() does not
> > provide any way of getting know if it was a local error or if it was
> > an error ev
On Mon, 7 Jul 2014 17:28:11 +0300
Pekka Paalanen wrote:
> From: Marek Chalupa
>
> When an error occurs, wl_display_get_error() does not
> provide any way of getting know if it was a local error or if it was
> an error event, respectively what object caused the error and what
> the error was.
>
From: Marek Chalupa
When an error occurs, wl_display_get_error() does not
provide any way of getting know if it was a local error or if it was
an error event, respectively what object caused the error and what
the error was.
This patch introduces a new function wl_display_get_protocol_error()
wh
