This week we made good strides in continuing to enhance the feature set of our game. I think Trello is working out nicely for utilizing an agile approach to identifying and assigning tasks. John is being an excellent PM by keeping everyone on track and making sure we don't go too far off into the weeds technically or creatively and forget the charter and the architecture we agreed on.
It sounds like Eric has some cool social elements (e.g. facebook, twitter) that will coming down the pipe and Lee is working on writing out our state (level reached, high score, etc.) through a file IO class. James is continuing to remind us why he's a good choice for architect as this week he has brought us some much needed re-factoring to the code base that is going to provide us a more object-oriented approach. We are utilizing the Corona SDK's built in story boarding that is helping with scene management and creating the different levels.
I spent this week adding pause functionality to the game. I added a pause button to the top left corner of the game that when pressed will suspend the world. Pausing the physics system and the update loop of the game was pretty straight forward though I was presented with a bit of challenge when I noticed as you unpaused the game the player would fire. I eventually tracked this down to the fire listener being triggered off a tap event which is really cued off the release (not the press) of the players finger. So as you touched to unpause the game, the subsequent release would be processed as a fire. I corrected this by adding a resuming flag that is set when unpausing and causes the listeners to ignore the event if resuming and then reset the flag. Fun stuff.
No comments:
Post a Comment