onPause() is the only reliable method to put code to be run on exit.
However, not much should be there except to save state if needed. Doing a
lot of work before exiting is a great way to get someone to uninstall your
app.
On Thu, May 13, 2010 at 3:43 PM, Moto wrote:
> What exactly are you tryin
Lee wrote:
> I have a service which starts an activity and waits for it to finish
> before proceeding.
Please don't do that.
If you explain what it is you are trying to accomplish here, perhaps we
can give you ideas on how to solve your business problem, rather than
helping you do something you s
The activity is started from a service: you can't use
startActivityForResult.
Previously I had the service checking via the ActivityManager whether
the activity was still running but it's not reliable enough.
Lee
On May 14, 11:04 am, Kostya Vasilyev wrote:
> You can do it the other way around -
You can do it the other way around - have your activity do something upon
successful completion. See startActivityForResult.
14 мая, 2010 11:27 AM пользователь "Lee"
написал:
I have a service which starts an activity and waits for it to finish
before proceeding.
It's not reliable to check using
I have a service which starts an activity and waits for it to finish
before proceeding.
It's not reliable to check using the Android API if the activity is
still running, so I'm using a static variable as a flag.
If the activity is somehow exited before it can set the flag, I've got
big problems.
What exactly are you trying to do?
On May 13, 9:34 am, Lee wrote:
> Is isFinishing() guaranteed to return true in onPause() when an
> activity is being killed by the system ?
>
> If not, how is it possible to differentiate activity-being-killed and
> one of the other reasons for onPause() being c
6 matches
Mail list logo
