1

I'm a bit confused about my intent lifecycle. I have a file browser which lets me nav to a particular graphic file, I fire up an intent to view that file and away we go. Back key returns me to the file browser. Also, from advice here (from Phylum Tea) I can now browse to a file via the web or a 3rd party file browser like Astro. All good.

My problem comes when, having opened a file from the web, it displays great, back key returns me to the web browser, but then when I choose a different file to view in my intent, the first file is still there. When I backed out of my viewer after the first file the intent remained alive and now (from the web browser) the subsequent files are not being passed through to the viewer, we are just bringing the original intent, with its contents, back into view.

So my Q: When using an intent to view a file brought in other-than through my inbuilt file browser, what do I do at onClose() to make sure the intent is terminated? And how do I distinguish that situation from opening a file via my own file browser?

Hope this makes sense!

tVm for any advice.

Baz

Community
  • 1
  • 1
Barry
  • 1,198
  • 3
  • 11
  • 27

1 Answers1

0

If I understand your question correctly your asking if you can control how long an Intent lasts? It's just a message, it doesn't bounce around in the System.

You fire off an Intent, an application catches it, reacts, and that is it.

thumbmunkeys
  • 20,144
  • 8
  • 56
  • 107
Woody
  • 363
  • 2
  • 14
  • Sorry, my misuse of terminology, for intent, read activity... B. – Barry Aug 16 '11 at 14:42
  • Actually, I'm having a couple of different problems which seem to be overlapping. I'll ask a fresh question when I work out what answer I'm looking for! Consider this question closed. tvm. – Barry Aug 16 '11 at 16:48