Re: New version of synchronization changes - windows not redirected



Thanks for the info, Adel.

Adel Gadllah writes:

Am 05.04.2013 05:15, schrieb Karl Tomlinson:
Should an application assume that a window manager advertising
_NET_WM_FRAME_DRAWN will always composite the window?
No the spec does not mandate that and mutter does not do that.

The spec does say that a "compositing window manager" MUST send "a
_NET_WM_FRAME_DRAWN client message immediately after finishing the
redrawing that results from an application frame."

If this is not requiring the manager to composite the window, then
I'm not clear whether a _NET_WM_FRAME_DRAWN message will be sent
if the compositing manager is not redrawing the window.

Is it sufficient for an application to check for
_NET_WM_FRAME_DRAWN in _NET_SUPPORTED before waiting for
_NET_WM_FRAME_DRAWN messages?

If so, I guess the window manager still needs to use SYNC counter
events to determine when to send _NET_WM_FRAME_DRAWN, even for
windows that are not redirected.

If not, there must be some way to know whether _NET_WM_FRAME_DRAWN
will be sent?

I'm assuming that it is not necessary to check the _NET_WM_CM_S[n]
selection owner in addition to _NET_WM_FRAME_DRAWN because
_NET_WM_FRAME_DRAWN would not be included when a window manager is
not compositing.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]