Actually qtmir can possibly keep using if (m_surface->buffers_ready_for_compositor(userId) > 0)
as it does already.
The problem then is that Mir reduces the return value of that function prematurely if called in that way. So maybe some fix is still possible in Mir itself.
Actually qtmir can possibly keep using if (m_surface- >buffers_ ready_for_ compositor( userId) > 0)
as it does already.
The problem then is that Mir reduces the return value of that function prematurely if called in that way. So maybe some fix is still possible in Mir itself.