singleInstance. Create a "history" machenism that stores the Intents this activity gets (it will get the first in onCreate and the rest on onNewIntent) so you'd be able to re-create the history of the requests.
Do notice that in either case, if your map activity is part of some chain of activities, you'll have a hard time maintaining the activity stack you want. On Wednesday, October 3, 2012 10:40:36 PM UTC+2, Partho Bhowmick wrote: > > I have an app with a number of activities, one of which subclasses > MapActivity. It has a single MapView. For reasons I won't go into, I have > situations where I may need more than instance of this MapActivity to be > launched. I know the Maps API docs says "Only one MapActivity is > supported per process. Multiple MapActivities running simultaneously are > likely to interfere in unexpected and undesired ways." > (link<https://developers.google.com/maps/documentation/android/reference/com/google/android/maps/MapActivity>). > > So, what are my options? Use a singleTask or singleInstance flag for this > MapActivity subclass? -- 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
