Yeah, I was trying to remember why I posted it delayed - and I think its because I was having the problem without the delay.
I suppose, even if the post is not delayed, the user might still back out before the openOptionsMenu gets to the front of the queue. Thanks - yeah, maybe use isFinishing() and possibly override it to set a flag when super.isFinishing() returns. isFinished() would have been nice! On 25 September 2010 23:48, TreKing <treking...@gmail.com> wrote: > On Sat, Sep 25, 2010 at 3:11 AM, Mark Carter <mjc1...@googlemail.com>wrote: > >> Is there any way to avoid this? >> > > Don't post it delayed? It's probably happening if a user clicks your app to > open it, then decides it was a mistake and tries to exit immediately after, > so the Activity is exiting by the time your Runnable runs. > > >> Maybe a test to see whether the activity is still running? If so, what is >> the most reliable way to do that? >> > > Maybe "isFinishing()"? > > > ------------------------------------------------------------------------------------------------- > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > transit tracking app for Android-powered devices > > -- > 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<android-developers%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- 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
