Timer Trouble

Ugh, this new timer and interpolation thing is giving me troubles. Initially I wasn’t even interested in a new timer class. My timer class was working just fine. The problem is Nick’s new and improved interpolation class comes with requires a new and improved timer class.

Of course getting the new timer to not shatter the code that the rest of the game was using for a timer has been, problematic at best. And I haven’t even actually begun to start messing with the interpolation class yet.

Since I don’t see it as good practice to have two timer classes in a program I’m faced with one of two choices. Either rewrite the rest of the game elements that currently access my timer class to use the new timer class. Or, rewrite parts of the new timer class to accept the calls that are currently in the existing game.

The one good thing coming out of all of this is the educational value of it since I’m starting to get into delegates and lambda expressions which is new stuff to me.

Tweening...stuff

I'm happy to report the further animation and collision tests have turned out positive, so with the new classes in place it's time to move on to the next thing. And after throwing a dart at the wall...it appears working in an interpolation class (or tweening class) is the next thing to tackle.

This interpolation class will be a utility class that will handle things like fading the screens up and down, moving menu items across the screen and who knows what else. So it will be a very handy thing to have around both now and in the future...so, let's get it right.

To start off I've been reading a lot from Nick Gravelyn's blog. And lucky for me he has an interpolation class that will serve as my base point of learning. You think that would be easy then huh? Well it appears I've got some reading up to do before I get rolling with it since Nick's using delgates and lambda expressions to implement his classes.

So for now I've got to get a handle on these two new elements...so, back to reading.