I've been trawling around the nets on Android key stuff.
Here's my take on it:
* The Back button (also known as the Up button) should peel one layer back on the app's stack of sub-launches. It should only force an exit if there's no other thing. Consequently, I now think that a sensible guideline would be that if one's game has a main menu, pressing Back should suspend the current activity, and return to the menu with the possibility of resuming, quitting, or doing something else.
Simply forcing a quit seems a little brutal. Maybe a requestor should be shown asking if you really want to quit. This is normal behaviour in most other contexts!
* The Home key cannot be overridden. It will Pause the running app, and go where ever Home is deigned to be on the device. Eventually, it will will halt the app if memory is low or it hasn't been accessed for a long time.
* Many new phones do not have physical keys. I have yet to see an AppGameKit game that implements the interface bar with Back, Home etc on. Has anybody tackled this issue?
Is Tier 1 properly handling the Home button? If so, how is the App coming out of hibernation after the Home button was pressed, and then the app icon pressed?
Likewise, does anybody have a short example of Tier 2 code showing how the app is notified that Home has been pressed, and later, that it has been re-started?
Very grateful for your thoughts and info!
-- Jim DO IT FASTER, EASIER AND BETTER WITH AppGameKit FOR PASCAL