2014/10/16 上午 08:09:27

android Programming Glossary: activity.finish

what exactly Activity.finish() method is doing?

http://stackoverflow.com/questions/10847526/what-exactly-activity-finish-method-is-doing

exactly Activity.finish method is doing I'm developing android applications for a while.. activity life cycle and application's life cycle. I know Activity.finish method calls somewhere in the way to Activity.onDestroy and..

How to kill my own Activity - the hard way

http://stackoverflow.com/questions/3241322/how-to-kill-my-own-activity-the-hard-way

So I have my Activity and on pressing a Quit button I call Activity.finish . This effectively closes my application. The problem The Dalvik.. my Activity from memory I'm looking for something like Activity.finish_and_kill_my_process_please call or something similar. android.. So I have my Activity and on pressing a Quit button I call Activity.finish . This effectively closes my application. Please don't do this..

Activity.finish() called but activity stays loaded in memory

http://stackoverflow.com/questions/4594996/activity-finish-called-but-activity-stays-loaded-in-memory

called but activity stays loaded in memory When I run my app.. main thread and 3 binder threads. On a button click I call Activity.finish which looks like it ends the activity as the UI closes and goes.. your app leaves main memory the OS does. Look closely at Activity.finish ... Call this when your activity is done and should be closed...

New Activity in Android “enter from the side”

http://stackoverflow.com/questions/4807131/new-activity-in-android-enter-from-the-side

you have some UI control that ends that activity and calls Activity.finish then you can just add the overridePendingTransition right after..

what exactly Activity.finish() method is doing?

http://stackoverflow.com/questions/10847526/what-exactly-activity-finish-method-is-doing

exactly Activity.finish method is doing I'm developing android applications for a while and followed a lot of posts about activity life cycle and.. applications for a while and followed a lot of posts about activity life cycle and application's life cycle. I know Activity.finish method calls somewhere in the way to Activity.onDestroy and also removing the activity from stack and I guess it somehow..

How to kill my own Activity - the hard way

http://stackoverflow.com/questions/3241322/how-to-kill-my-own-activity-the-hard-way

to kill my own Activity the hard way So I have my Activity and on pressing a Quit button I call Activity.finish . This effectively closes my application. The problem The Dalvik process of my application is still hanging around as a.. somehow kept alive for no good reason. How can I really remove my Activity from memory I'm looking for something like Activity.finish_and_kill_my_process_please call or something similar. android process activity kill share improve this question So.. process activity kill share improve this question So I have my Activity and on pressing a Quit button I call Activity.finish . This effectively closes my application. Please don't do this . The Dalvik process of my application is still hanging around..

Activity.finish() called but activity stays loaded in memory

http://stackoverflow.com/questions/4594996/activity-finish-called-but-activity-stays-loaded-in-memory

called but activity stays loaded in memory When I run my app on the debugger I get the main thread and 3 binder threads... in memory When I run my app on the debugger I get the main thread and 3 binder threads. On a button click I call Activity.finish which looks like it ends the activity as the UI closes and goes back to the home screen. However in the debugger it still.. share improve this question You don't control when your app leaves main memory the OS does. Look closely at Activity.finish ... Call this when your activity is done and should be closed. The ActivityResult is propagated back to whoever launched..

New Activity in Android “enter from the side”

http://stackoverflow.com/questions/4807131/new-activity-in-android-enter-from-the-side

coming back to the original one it's a bit more foggy. If you have some UI control that ends that activity and calls Activity.finish then you can just add the overridePendingTransition right after that. To handle the case where the user ends the activity..