Mir

  1. Bug #1216472
  2. Comment #14

Comment 14 for bug 1216472

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

OK, I've figured out a terrible hack that seems to solve the problem (although it generates constant damage and constant CPU usage):

_X_EXPORT RegionPtr
xmir_window_get_dirty(xmir_window *xmir_win)
{
    return &xmir_win->region; /* Terrible hack */

This seems to solve the bug, suggesting xmir_window_get_dirty is returning incorrect damage regions.

It's not definitive and not a fix. But looks like good progress.