On Fri, 2017-03-10 at 08:34 +0100, Pavel Grunt wrote:
> On Thu, 2017-03-09 at 22:00 +0100, Victor Toso wrote:
> > On Thu, Mar 09, 2017 at 04:51:24PM +0100, Pavel Grunt wrote:
> > > SPICE_DISPLAY_DEBUG provides information about channel and
> > > monitor
> > > ids.
> >
> > Yes, makes sense to me. W
On Thu, 2017-03-09 at 22:00 +0100, Victor Toso wrote:
> On Thu, Mar 09, 2017 at 04:51:24PM +0100, Pavel Grunt wrote:
> > SPICE_DISPLAY_DEBUG provides information about channel and monitor
> > ids.
>
> Yes, makes sense to me. We have CHANNEL_DEBUG, I would go with
> DISPLAY_DEBUG instead.
Okay
>
On Thu, Mar 09, 2017 at 04:51:24PM +0100, Pavel Grunt wrote:
> SPICE_DISPLAY_DEBUG provides information about channel and monitor ids.
Yes, makes sense to me. We have CHANNEL_DEBUG, I would go with
DISPLAY_DEBUG instead.
> In case of multimonitor it helps to identify the owner of the debug
> mess
SPICE_DISPLAY_DEBUG provides information about channel and monitor ids.
In case of multimonitor it helps to identify the owner of the debug
message.
---
I am currently looking at a bug related to not working keyboard grab
in multimonitor env, and it was not clear which widget is receiving
focus eve
