I think I understand the termination process a bit better now. I guess calling finish() on an activity (and finish() will execute immediately) it is as if you are "scheduling it" for termination by the OS. And I guess that will justify the existance of the finishing() method that can return that a particular activity has been requested to terminate.
On Aug 27, 10:41 pm, kypriakos <demet...@ece.neu.edu> wrote: > > > I am wondering if it is possible to exit the activity but > > > subsequently > > > ask Android to terminate it immediately ... > > > If by "it", you mean "the process", please do not do this. Please let > > Android terminate it when it is ready to. Whatever problem you are > > trying to solve can be solved better some other way. > > I know I know - and thus the questions. I don't feel it's the right > thing > to do by doing so and I am trying to find a way around it. > > > > > > On a different note - how far back do your books go? Did you cover > > > 1.6 and 2.1? > > > Yes. 1.5, even. Mostly, I cover "Android" and try to point out when > > various new-ish features were added to the OS. > > Good! That's a good approach. I like to study the OS but through its > transitions and the lessons learned. I will check them out. > > Ack on the rest - good info. Thanks. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en