> An alternative approach is to separate your simulation loop and your rendering loop.
or at the very least, calculate a timing delta to determine animation values. On Fri, Apr 28, 2017 at 9:48 PM Zellyn <zel...@gmail.com> wrote: > Yes, the racy boolean access made me cringe but I was going for short :-) > > Your suggestion to disentangle rendering from emulation is a good idea... > now that I understand what's happening! > > The really funny thing is that my emulator looked suspiciously close to > the right speed: since I was calling the shiny update once per emulated > frame, if it was delaying to the next 60th of a second, it may be *exactly* > correct :-) > > Thanks for the help. And for shiny! > > Zellyn > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
