Android Question Activity.Finish issue

Got you

Thinking about it I do already use that method with the Material Drawer to avoid building a chain of past activities.

MaFu said:

If you press the back button the current Activity will be finished, no need to catch the button and call Activity.Finish there.

Click to expand...

Not quite. Imagine that you call from activity2, and Activity3 that is nothing but a form... you complete half the form, and in the way of doing it, you set a few variables... Now you hit the back Button, but you dont call activity.finish... You re-enter Activity3... althou the text fields may be empty, depending on your code, the previously set variables are unchanged (as opposed to being empty, null, or have a default value). This may cause your activity to produce results differently than if it had called activity.finish

Seems to me that (optionally) more control should be handed to the developer so that when necessary we can properly kill off stuff not needed.

Cableguy said:

Not quite. Imagine that you call from activity2, and Activity3 that is nothing but a form... you complete half the form, and in the way of doing it, you set a few variables... Now you hit the back Button, but you dont call activity.finish... You re-enter Activity3... althou the text fields may be empty, depending on your code, the previously set variables are unchanged (as opposed to being empty, null, or have a default value). This may cause your activity to produce results differently than if it had called activity.finish

Click to expand...

On close of Activity 3 Activity_Pause() is called.
On reenter Activity 3 Activity_Create() and Activity_Resume() is called.
Regardless if i hit the back button or call Activity.Finish.
Why should a variable value differ?

imagine this, Activity3 is a set-up activity, where you define for example, a typeface for the text of some of your views.
now imagine that you set the typeface variable to a value from a dropdown list, but form no matter what reason, like a phonecall, sms, etc, a system app over-imposes itself over your app, sending your activity to background... still following me?
Imagine too that, you didn't feel necessary to create a failsafe feature in order to save the form current status if your activity loss focus. When re-entering your activity, the textfields will be empty, BUT the variables that where set, are still set to the values chosen before losing focus?

PS. maybe my example is a bit Odd...

This example is only a software design fault of the developer
You should always save and restore the values of the entry fields in this case.
If the user must re-enter the data because of an interrupt he wish you (the developer) to hell

MaFu said:

This example is only a software design fault of the developer
You should always save and restore the values of the entry fields in this case.
If the user must re-enter the data because of an interrupt he wish you (the developer) to hell

Click to expand...

I agree, BUT it is the way it would behave if nothing is coded to prevent it....

as I said, it was an example... an odd one

Would this might help? https://www.b4x.com/android/forum/t...applications-settings-and-state.9777/#content

James Chamblin said:

Would this might help? https://www.b4x.com/android/forum/t...applications-settings-and-state.9777/#content

Click to expand...

Sure, it's simplifies the save state procedure. But it's only one way of many to resolve the problem.
Whatever you do, it's only important that you must save and restore the state.