compositor: clarify update_transform vs. repaint
authorPekka Paalanen <ppaalanen@gmail.com>
Thu, 9 Feb 2012 13:58:44 +0000 (15:58 +0200)
committerPekka Paalanen <ppaalanen@gmail.com>
Fri, 10 Feb 2012 13:47:56 +0000 (15:47 +0200)
commitb45ac5eada9f311d1e31ff7337b3de091434e6a1
treecf3811c373a0b1636201947f5dd840f7ce048976
parent965167807000f1b6885a725579e57c0b8ad5c10d
compositor: clarify update_transform vs. repaint

Remove redundant weston_surface_update_transform() calls from within
output repaint paths, and add a comment that we need to rely on
surface->geometry.dirty == 0 within the repaint sub-functions.

Now that weston_surface_update_transform() does damage as needed, and
weston_output_repaint() explicitly calls update_transform, we can reduce
the updates in rotate_grab_motion() to simply scheduling a repaint. This
will guarantee that the change in rotation ends up on screen ASAP.

Signed-off-by: Pekka Paalanen <ppaalanen@gmail.com>
src/compositor.c
src/shell.c