simple-damage: fix rotating-transform option
Compare changes
There are no changes yet
No changes between master and master
Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
The migration is almost done, at least the rest should happen in the background. There are still a few technical difference between the old cluster and the new ones, and they are summarized in this issue. Please pay attention to the TL:DR at the end of the comment.
If --rotating-transform
is set, the damage calculation of the previous position of the ball has to be done with the old transform value, not the already updated one.
Note: this is still broken when using in combination with surface damage and viewport, as it's a rather complicated scenario and surface-damage is kinda legacy anyways.
This helps a lot on weston but there seem to be some some issues left in the compositor.
On mutter with https://gitlab.gnome.org/GNOME/mutter/merge_requests/121 it renders perfectly, with or without --use-damage-buffer
.
Helps with: #155
Context: !41 (comment 54445)
No changes between master and master