2016-03-30 21:26 GMT+03:00 Bryce Harrington :
> On Wed, Mar 30, 2016 at 09:05:07AM +0300, Giulio Camuffo wrote:
>> 2016-03-30 2:10 GMT+03:00 Bryce Harrington :
>> > On Wed, Mar 23, 2016 at 04:31:16PM +0200, Giulio Camuffo wrote:
>> >> The new wl_display_add_protocol_logger allows to set a function
On Wed, Mar 30, 2016 at 09:05:07AM +0300, Giulio Camuffo wrote:
> 2016-03-30 2:10 GMT+03:00 Bryce Harrington :
> > On Wed, Mar 23, 2016 at 04:31:16PM +0200, Giulio Camuffo wrote:
> >> The new wl_display_add_protocol_logger allows to set a function as
> >> a logger, which will get called when a new
2016-03-30 2:10 GMT+03:00 Bryce Harrington :
> On Wed, Mar 23, 2016 at 04:31:16PM +0200, Giulio Camuffo wrote:
>> The new wl_display_add_protocol_logger allows to set a function as
>> a logger, which will get called when a new request is received or an
>> event is sent.
>> This is akin to setting W
On Wed, Mar 23, 2016 at 04:31:16PM +0200, Giulio Camuffo wrote:
> The new wl_display_add_protocol_logger allows to set a function as
> a logger, which will get called when a new request is received or an
> event is sent.
> This is akin to setting WAYLAND_DEBUG=1, but more powerful because it
> can
The new wl_display_add_protocol_logger allows to set a function as
a logger, which will get called when a new request is received or an
event is sent.
This is akin to setting WAYLAND_DEBUG=1, but more powerful because it
can be enabled at run time and allows to show the log e.g. in a UI view.
Sign
