I'm trying to understand the limits of startActivityForResult(), so I can simplify my onActivityResult() logic.
An Activity can make back-to-back calls to startActivityForResult() in a single method execution, seemingly kicking off multiple concurrent sub-Activities. The startActivityForResult() method doesn't complain. A sub-Activity will return a successful result in at least some cases (I've played with this). Maybe that's only true for Activities that don't have a GUI, such as TextToSpeech.Engine.ACTION_CHECK_TTS_DATA? Are such sub-Activities really being executed concurrently? Or is Android maybe queueing the requests for serial execution? Or...? Some "best practices" questions: 1) If it is indeed possible to kick off concurrent sub-Activities, are there situations where that's actually a good thing to do? 2) Is a non-GUI Activity sometimes a good implementation strategy, for certain problems? -Mark -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
