Don't have an account yet? Then register once and completely free of charge and use our wide range of topics, features and great options. As a registered member on our site, you can use all functions to actively participate in community life. Write posts, open topics, upload your pictures, put your videos online, talk to other members and help us to constantly improve our project and grow together! So, what are you waiting for? Become a part of us today!
Login or registerTo get support for a technical issue such as installing the software, to query a purchase that you've made/would like to make, or anything other than using our software, please visit our Customer Service Desk:
Open a Ticket
I'll work on it before the end of the week.
Just a thing : what I will investigate is the Quit application action that does not work.
You have to detect manually when the first press on back occurs (or when the user pressed back enough time to come back to the first position), and decide to quit the application your self. I cant do it myself as I do not know at all what you do in your application.
-> Use the XNA object to detect a press on BACK
-> When it occurs, simply do a End Application.
Can you test and tell me if it works?
Correct. It's the going back to a menu behavior, not quitting, that is more critical.
Cyberbeard, the timer workaround discussed in the other back button thread worked for me - but it is still touchy.
Could it be that the button press is triggering while held down, not when pressed? I know this is the case with a lot of exporter input conditions, where an 'is x button pressed' will act the same as a 'repeat while key is pressed' command as opposed to a 'upon key press' for example.
So it could be that the button being pressed is causing the app to go back to the main menu or whatever, then it immediately quits because the button is still down, triggering your quit event.
Take out the 'end application' event in your main menu and test it, if it doesn't quit then this is what's happening. You can code around this by having a check for the button not being pressed before 'activating' the button again:
-Create a value with default of 1 called 'buttonpress'
-Create an event 'if button *isn't* pressed' then set 'buttonpress' to 0.
-Add 'buttonpress' == 0 as a condition on your button press event.
With this method you can avoid button press events triggering across multiple frames.
I was about to make the same suggestion : maybe the back button down condition of the first frame is triggered when you come back from a later frame.
The value cole is talking about should be global of course.
This solution worked wonderfully well when I made sure to set the global 'buttonpress' value to 1 at the 'Start of each Frame'.
Thank you both. 
OK goog news. I will implement this in the XNA object itself so you wont need to do it yourself.
Don’t have an account yet? Register yourself now and be a part of our community!
Almightyzentaco (Fusion 2.5 Tutorials)
Captain Quail (Firefly Tutorials)
