simple-damage: fix rotating-transform option

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)

mentioned in issue #155

changed the description

added 1 commit

• dc112af8 - simple-damage: fix rotating-transform option

Compare with previous version

changed title from simple-damage: fix --rotating-transform --use-damage-buffer to simple-damage: fix rotating-transform option

changed the description

added 1 commit

• 8fc8542b - simple-damage: fix rotating-transform option

Compare with previous version

changed the description

added Clients label

added 114 commits

• 8fc8542b...2d4cc4f4 - 114 commits from branch wayland:master

Compare with previous version

added 30 commits

• 2d4cc4f4...cc64cc37 - 30 commits from branch wayland:master

Compare with previous version

What is the status of this? It seems like there's no commit in this MR anymore.

Eh that's weird...probably pushed something wrong...will update it again, soon.

added 80 commits

• cc64cc37...2edbcbd9 - 80 commits from branch wayland:master

Compare with previous version

added 54 commits

• 2edbcbd9...5d7877ad - 54 commits from branch wayland:master

Compare with previous version

GitLab still says there are zero commits.

found the commit again...bad idea to create a MR from the master branch :) will close this one and open a new MR

closed

mentioned in merge request !222 (closed)

Reopened at !222 (closed)