Hi! Currently there is only one exit point from app located in SDLActivity.onDestroy() which called only by android system when it needs more resources. But most of the time we need to close app at the moment, i.e. clicking on the exit button. In this case we just exit SDL thread, not the application.
I see commented call to exit() in SDL_android_main.cpp, however killing process is not good way to exit android app as it doesn’t respect android life cycle, we can’t release some resources, services etc.
My idea is to add proper call to Activity.finish() just after SDL thread quits (using commands).
What do you think about it? Is everything so simple?
p.s> Anyway for my app I will add call exit() in onDestroy() method because I have static data in my native library and it must be reloaded every time app starts.
I have a patch pending for letting android application to exit the app!Its
like the way you are proposing.You have to call finish just before the
thread is destroyed.On Thu, Jun 6, 2013 at 6:57 PM, mastermind <denis.barkar at gmail.com> wrote:
**
Hi! Currently there is only one exit point from app located in
SDLActivity.onDestroy() which called only by android system when it needs
more resources. But most of the time we need to close app at the moment,
i.e. clicking on the exit button. In this case we just exit SDL thread, not
the application.
I see commented call to exit() in SDL_android_main.cpp, however killing
process is not good way to exit android app as it doesn’t respect android
life cycle, we can’t release some resources, services etc.
My idea is to add proper call to Activity.finish() just after SDL thread
quits (using commands).
What do you think about it? Is everything so simple?
p.s> Anyway for my app I will add call exit() in onDestroy() method
because I have static data in my native library and it must be reloaded
every time app starts.
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
Dimitris Zenios wrote:
I have a patch pending for letting android application to exit the app!Its like the way you are proposing.You have to call finish just before the thread is destroyed.?
Hi! Currently there is only one exit point from app located in SDLActivity.onDestroy() which called only by android system when it needs more resources. But most of the time we need to close app at the moment, i.e. clicking on the exit button. In this case we just exit SDL thread, not the application.I see commented call to exit() in SDL_android_main.cpp, however killing process is not good way to exit android app as it doesn’t respect android life cycle, we can’t release some resources, services etc.
My idea is to add proper call to Activity.finish() just after SDL thread quits (using commands).
What do you think about it? Is everything so simple?
p.s> Anyway for my app I will add call exit() in onDestroy() method because I have static data in my native library and it must be reloaded every time app starts.
SDL mailing list
SDL at lists.libsdl.org (SDL at lists.libsdl.org)
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org (http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org)
Does the patch also applies to iOS? I have the same issue there.
The exit call is also commented (in SDL_uikitappdelegate.m).
Thanks!> On Thu, Jun 6, 2013 at 6:57 PM, mastermind <denis.barkar at gmail.com (denis.barkar at gmail.com)> wrote: