[PATCH] client: extend error handling

2014-06-20 Thread 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() which will return error

Re: [PATCH] client: extend error handling

2014-06-20 Thread Marek Chalupa
Thanks for reviewing :) English is my weakness (not the only though :D). Fixed patch is coming... Marek On 19 June 2014 04:24, Bryce W. Harrington wrote: > On Mon, May 26, 2014 at 04:57:23PM +0200, Marek Chalupa wrote: > > When an error occurs, wl_display_get_error() does not > > provide any w

Re: [PATCH] client: extend error handling

2014-06-18 Thread Bryce W. Harrington
On Mon, May 26, 2014 at 04:57:23PM +0200, Marek Chalupa wrote: > 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 introdu

[PATCH] client: extend error handling

2014-05-26 Thread 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() which will return error

Re: [PATCH] client: extend error handling

2014-04-30 Thread Pekka Paalanen
On Wed, 30 Apr 2014 09:40:19 +0200 Marek Chalupa wrote: > On 24 April 2014 14:45, Pekka Paalanen wrote: > > > On Wed, 23 Apr 2014 14:39:48 +0200 > > Marek Chalupa wrote: > > > > > +/** > > > + * This function is called for error events > > > + * and idicates that in some object occured an erro

Re: [PATCH] client: extend error handling

2014-04-30 Thread Marek Chalupa
On 24 April 2014 14:45, Pekka Paalanen wrote: > On Wed, 23 Apr 2014 14:39:48 +0200 > Marek Chalupa wrote: > > > When an error occurres, than wl_display_get_error() do not > > ... occurs, [then] ... does not > > > provide any way of getting know if it was a local error or if it was > > an error e

Re: [PATCH] client: extend error handling

2014-04-24 Thread Pekka Paalanen
On Wed, 23 Apr 2014 14:39:48 +0200 Marek Chalupa wrote: > When an error occurres, than wl_display_get_error() do not ... occurs, [then] ... 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

[PATCH] client: extend error handling

2014-04-23 Thread Marek Chalupa
When an error occurres, 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 e