On 19 April 2014 10:22, Pekka Paalanen wrote:
> On Fri, 18 Apr 2014 12:27:59 +0200
> Marek Chalupa wrote:
>
> > On 15 April 2014 15:36, Pekka Paalanen wrote:
> >
> > > On Fri, 11 Apr 2014 11:39:13 +0200
> > > Marek Chalupa wrote:
> > >
> > > > When an error occures, than wl_display_get_error()
On Fri, 18 Apr 2014 12:27:59 +0200
Marek Chalupa wrote:
> On 15 April 2014 15:36, Pekka Paalanen wrote:
>
> > On Fri, 11 Apr 2014 11:39:13 +0200
> > Marek Chalupa wrote:
> >
> > > When an error occures, than wl_display_get_error() do not
> > > provide any way of getting know if it was a local
On 15 April 2014 15:36, Pekka Paalanen wrote:
> On Fri, 11 Apr 2014 11:39:13 +0200
> Marek Chalupa wrote:
>
> > When an error occures, than wl_display_get_error() do not
> > provide any way of getting know if it was a local error or if it was
> > an error event, respectively what object caused t
On Fri, 11 Apr 2014 11:39:13 +0200
Marek Chalupa wrote:
> When an error occures, than wl_display_get_error() do 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 introduc
When an error occures, than wl_display_get_error() do 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()
which will return er