Developments

After finally getting my Forge/NewYA stuff working, I figured I should let TeamOUYA take a look at what I've got so far. The feedback was roughly "Needs an Exit button".
Because the Forge doesn't have the big obvious "OUYA BUTTON" that the OUYA controller has, it's much harder to assume the player has a single button to exit the game. As such, I spent a fair amount of time, yesterday, adding a Quit button into my frameworks.
I now need to replace old menus with new menus, incorporating the new Quit button, then recompile for the "NewYA" target, before submitting each game for retesting purposes.
I'll be attempting the first couple of those, today, hopefully.



And there it is! A simple enough reuse of an image that was already in the engine, plonked amongst the standard menu system.

I'll have to delve a little deeper for some of the games, though, as not all my OUYA games use the basic menu.
Games like JNKBombers and Green's Mini Quest have their own unique menus, and will obviously take a little more planning to get them to show a nice button.

Note : The Quit button is currently an OUYA/Android exclusive button. I might also add it to the Windows exe target, but that means recompiling and uploading all of those, too!
On HTML5, hitting the quit button simply stops the javascript in it's tracks, leading to what appears to be a frozen, broken game.
Curious!! I'll, obviously, be leaving the Quit button off the HTML5 target!!

-=-=-

Daily Doodle : In the Garage

Platdude's car appears to be broken.. Again.. So he's diving right in to see if he can solve the problem.
.. Again..
*tsk* Cars. They're not easy, are they?

Mailbag : Empty

If you'd like to stuff my mailbag, (Please do!!) you can do so right here, at https://bit.ly/AGAW_Mail. Send comments, questions, game ideas, thoughts and more, and they'll probably turn up here, eventually.