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
On 5 May 2014 15:02, Pekka Paalanen ppaala...@gmail.com wrote:
On Wed, 30 Apr 2014 10:11:01 +0200
Marek Chalupa mchqwe...@gmail.com 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,
On Wed, 7 May 2014 16:21:24 +0200
Marek Chalupa mchqwe...@gmail.com 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
On Wed, 30 Apr 2014 10:11:01 +0200
Marek Chalupa mchqwe...@gmail.com 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
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
