diff options
author | Neil Roberts <neil@linux.intel.com> | 2011-01-24 11:56:09 +0000 |
---|---|---|
committer | Neil Roberts <neil@linux.intel.com> | 2011-01-24 11:56:09 +0000 |
commit | 6b4f80bd6fd56f7b16ae89c1833500819e36e455 (patch) | |
tree | b5736eba831533c4aa511bfdba4d729118c47311 | |
parent | 333084b1f573fffee0b1aba7e378e3ff0e622dc4 (diff) | |
download | clutter-6b4f80bd6fd56f7b16ae89c1833500819e36e455.tar.gz |
clutter-timeline: Emit the new-frame signal even on the first frame
ClutterTimeline has special handling for the first time do_tick is
called which was not emitting a new-frame signal. This meant that an
application which directly uses the timeline would have to manually
setup the initial state of an animation after starting a timeline to
avoid painting a single frame with the wrong state. It seems to make
more sense to instead emit the new-frame signal so that the
application always sees a new-frame when the progress changes before a
paint.
(cherry picked from commit 5c0aaf50a7b3d1914d4580d5f853faa9a4b10f73)
Conflicts:
clutter/clutter-timeline.c
-rw-r--r-- | clutter/clutter-timeline.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/clutter/clutter-timeline.c b/clutter/clutter-timeline.c index 1f7c7f1fc..f1690c8c3 100644 --- a/clutter/clutter-timeline.c +++ b/clutter/clutter-timeline.c @@ -1225,7 +1225,9 @@ clutter_timeline_do_tick (ClutterTimeline *timeline, if (priv->waiting_first_tick) { priv->last_frame_time = *tick_time; + priv->msecs_delta = 0; priv->waiting_first_tick = FALSE; + clutter_timeline_do_frame (timeline); } else { |