Tizen back button not exiting app?

jonmulcahy

anyone else see this with recent builds? The past 3 games I've built the back button works fine when I define it to go from scene to scene, but when you hit it to exit the game nothing happens.

builds I made when tizen was first released work fine when exiting.

anyone else notice this?

@blackcloakGS

tarsiustudio

in the cookbook http://cookbook.gamesalad.com/tutorials/10/parts/69 says to put the pin back in every scene except the first. I guess no need to put the back button to exit the game

jonmulcahy

in the cookbook http://cookbook.gamesalad.com/tutorials/10/parts/69 says to put the pin back in every scene except the first. I guess no need to put the back button to exit the game

yea that's the part that doesn't work. in a few of my games, if there is no back button rule nothing happens.

izam

3 games submitted got rejected after 6 days in review because of this as well.

pHghost

I also just got rejected because of this!

CodeMonster

my app got accepted and i dont have a back button to exit the app

jonmulcahy

I did some further testing today, and it looks like if you have the back button rule anywhere in a scene, even within a sub rule, it will prevent the app from exiting. The back button will only exit the app if no other back rules exist.

IsabelleK

I don't have such issue. One of my games was approved few hours ago.

pHghost

It is quite a mystery. One of my apps got in, two got rejected. The behavior should be uniform across all of them, no differences in implementation -- meaning none.

quantumsheep

Forgive my ignorance/stupidity, but what do you actually put in the 'back' button.

I mean, on the title screen, I've set up a button and in it is the rule

If you press key back (back is written as opposed to choosing a key)

The rest is blank.


What do you put???

QS =D

jonmulcahy

lets say you have two scenes, a main menu and the game scene.

you need a rule in the game scene that says when key back is pressed, goto scene main menu.

in the main menu scene you don't put any rules, and when the user hits the back button, the game quits.

quantumsheep

lets say you have two scenes, a main menu and the game scene.

you need a rule in the game scene that says when key back is pressed, goto scene main menu.

in the main menu scene you don't put any rules, and when the user hits the back button, the game quits.

Ok, well you can always get back to the main screen somehow in my games, so that should be ok.

I still have no idea on the main menu back button though. You make one yourself, right? And put in the rule as I did into that button - with just 'if 'back' is pressed'?

Does it automatically exit if set up like that?

And when you say 'main menu scene you don't put any rules' do you mean none in the whole scene? Seems unlikely. So do you mean you have a button that just has the rule as I describe???

*feeling stupid here*

QS =D

jonmulcahy

yea i mean none in the whole scene if GS find's the back button in a rule in the scene it will attempt to run the rule's contents. if no back button rule is found, it exits the game.

quantumsheep

Thanks for the help, but it makes no sense to me right now - it's 4am - I think I'll leave it till morning!

QS =D

quantumsheep

So I didn't go to bed.

It seems that I need to put an additional rule into all my 'back' buttons in current games.

So, for example:

If I'm in the main game and finish a level, I would put a rule in the 'home' button that would say:

If key 'back' is pressed
Go to main menu

This would be in addition to any other rules I already have in the home button e.g.

if home button is touched
Go to main menu


So essentially, adding an extra rule to take into account the PHYSICAL back button.

Then, on the main menu, make sure that the rule 'if key 'back' is pressed' does not exist anywhere in that scene.

Then with no rule defined for the physical back key, it'll default to leaving the app.

Is that right? Have I got it right?

If that IS right, what happens if we have lots of menu stuff in one scene?

For example, in the menu scene I'm changing origin X to move between Title Screen and options.

There's a 'back' button in options to move the origin back to the Title Screen.

Technically it's acting like a 'back' button but isn't changing scene.

But if I add the physical back button rule, it won't exit the app from the Main menu scene. Right?

Does that make sense? And what have people done about it?

Cheers!

QS =D

colander

So I didn't go to bed.

It seems that I need to put an additional rule into all my 'back' buttons in current games.

So, for example:

If I'm in the main game and finish a level, I would put a rule in the 'home' button that would say:

If key 'back' is pressed
Go to main menu

This would be in addition to any other rules I already have in the home button e.g.

if home button is touched
Go to main menu


So essentially, adding an extra rule to take into account the PHYSICAL back button.

Then, on the main menu, make sure that the rule 'if key 'back' is pressed' does not exist anywhere in that scene.

Then with no rule defined for the physical back key, it'll default to leaving the app.

Is that right? Have I got it right?

QS =D

Correct and you will also need to account for any actions your Home button would have done if it were pressed.

If that IS right, what happens if we have lots of menu stuff in one scene?

For example, in the menu scene I'm changing origin X to move between Title Screen and options.

There's a 'back' button in options to move the origin back to the Title Screen.

Technically it's acting like a 'back' button but isn't changing scene.

But if I add the physical back button rule, it won't exit the app from the Main menu scene. Right?

Does that make sense? And what have people done about it?

Cheers!

QS =D

Obviously Tizen won't know you have both menus on the same scene and even if they did they will expect still it to work the way they want it to work. I think the easiest solution would be to recreate your Options menu on separate scene. That is a tough one and someone may have a better solution for it. Hard to see how if you have a back rule on the scene then the physical Back button won't exit the app.

quantumsheep

Correct and you will also need to account for any actions your Home button would have done if it were pressed.

Alright then! All done and ready to test!

Obviously Tizen won't know you have both menus on the same scene and even if they did they will expect still it to work the way they want it to work. I think the easiest solution would be to recreate your Options menu on separate scene. That is a tough one and someone may have a better solution for it. Hard to see how if you have a back rule on the scene then the physical Back button won't exit the app.

Poodoo. Well that's a hassle

jonmulcahy

I just put an extra splash screen and had a rule that brought be to that. Then if they hit back on that screen it would exit

Armelline

Did you find this problem occurred in the emulator as well, or did it work as expected in the emulator?