Commits on Source (5)
-
Whenever a view is moved, we should schedule a repaint for the outputs the view is on. This avoids users having to do it by hand every time they change something. There is no change in determinism of behaviour (e.g. 'I can reconfigure views as often as I like and it won't take effect until I schedule a repaint' isn't true, because output repaints might happen for reasons outside your control). Signed-off-by: Daniel Stone <daniels@collabora.com>
259420dd -
We don't need to explicitly schedule a repaint once we've reconfigured some views. Signed-off-by: Daniel Stone <daniels@collabora.com>
760d60f5 -
There's no need to call weston_view_schedule_repaint() once we've updated view properties. Signed-off-by: Daniel Stone <daniels@collabora.com>
bd97abf1 -
We don't need to manually schedule a repaint after we've updated our views - which happens as a side effect of destroying the transform/etc within the animation. Signed-off-by: Daniel Stone <daniels@collabora.com>
6da16f09 -
We don't need to manually schedule a repaint when we've moved the view for a drag & drop icon. Signed-off-by: Daniel Stone <daniels@collabora.com>
fdc0bafd