It looks like you're new here. If you want to get involved, click one of these buttons!
I couple of years ago I started a little project in Processing, just for the fun of it. Now, after learning masses amounts of coding and with help from a lot of you clever brains on this forum I have a little game running on my Android that I would like to publish. But there's one thing holding me off and bugging me: back button behaviour.
My game has a menu screen from where the player can pick a level, this will take him to the level. On screen I have a back button scripted to take the player back to the menu. But the default instinct of any Android user is to use the 'Back-Button' on the bottom of the device to step back in his navigation, expecting to navigate back to the menu. But with Processing this results in exiting or killing the application.
I know this topic has been discussed in the past, but it seems there have not been any decent solutions. People have suggested overriding or catching the behaviour and killing the buttons functionality before they get executed. I've tested these methods, but none of them work. At least not for me. And rightfully some of you have pointed out that this is the native behaviour of Android, which can't be changed (the back button either steps back in activity, if available, otherwise it kills the application).
I respect that, but I very much would like to find a solution in whatever form. I wouldn't want to launch a game that throws people off because it doesn't respond as they would expect.
Are there any clever ideas, any work-arounds, anything I've missed? Anyone that encountered the same issue and managed to resolve it in whatever way.
I'm on currently on Processing 3.3.6 And unfortunately I have little to no experience with Android Studio or Eclipse (yet).