search

KazDragon / paradice9

Telnet Chatter in C++14
Other
8 stars 2 forks source link

Improvement: Generalise animation routines #120

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
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 matthew....@gmail.com on 25 Oct 2012 at 5:26

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Moved to Milestone 1.4, since access to the context (and hence GUI strand) 
would be very useful here.

Original comment by matthew....@gmail.com on 30 Aug 2013 at 7:55

GoogleCodeExporter commented 9 years ago

Original comment by matthew....@gmail.com on 30 Aug 2013 at 7:56

GoogleCodeExporter commented 9 years ago

Original comment by matthew....@gmail.com on 6 Sep 2013 at 8:49