For starters, you can try using the Activity nostory flag in the manifest. This will make sure an Activity is finished if navigated away from developer.android.com/guide/topics/manif....
For starters, you can try using the Activity nostory flag in the manifest. This will make sure an Activity is finished if navigated away from. developer.android.com/guide/topics/manif....
Thanks for the quick answers. I tried to add the following line to the -app. Xml file in the android.
ManifestAdditions section. Since I am developing the app in Flex 4.5, I believe this is where it needs to go. "".
It doesn't make a difference. Am I doing someting wrong or are there other things I can try? – Mad Oxyn Jun 24 at 10:18.
This is how Android applications are supposed to work. See here: developer.android.com/guide/topics/funda... Your application's process is in either the "background" state (if the user pressed how) or "empty" state (if the user pressed back).
Event when I use the back button, the app remains running in the background. I see it active in the task manager and I can close it from there. – Mad Oxyn Jun 24 at 10:20 Yes as described on the link I pointed to, empty processes are kept around for a while so that if the user returns from them they don't need to be re-launched.
– hackbod Jun 25 at 5:26.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.