Improvement: Generalise animation routines

[GoogleCodeExporter]

Currently, each component with animation (clock, status bar) must maintain its 
own deadline timer, and get technical with the waiting.

They're also wrong (because they don't wrap the async_wait in the GUI strand), 
but that's beside the point.

More ideally, a component would carry its own deadline timer, which it would 
initialise on the first draw().

A function in component called "next_animation(ctx, time)" would schedule the 
next callback (on the GUI strand) for a certain time.  This would fire through 
a weak_ptr thunk eventually to a virtual method called do_animate.

Original issue reported on code.google.com by [email protected] on 25 Oct 2012 at 5:26

• Blocking: Improvement: Proper statusbar component #104
• Blocked on: Request: Allow the Graphics Context to be accessed at all times #131

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Moved to Milestone 1.4, since access to the context (and hence GUI strand) 
would be very useful here.

Original comment by [email protected] on 30 Aug 2013 at 7:55

• Added labels: Milestone-Release1.4
• Removed labels: Milestone-Release1.2
• Now blocked on: Request: Allow the Graphics Context to be accessed at all times #131

[GoogleCodeExporter]

Original comment by [email protected] on 30 Aug 2013 at 7:56

• Added labels: Priority-Medium
• Removed labels: Priority-High

[GoogleCodeExporter]

Original comment by [email protected] on 6 Sep 2013 at 8:49

• Added labels: Milestone-Release1.6
• Removed labels: Milestone-Release1.4