On Tue, Mar 15, 2011 at 9:25 AM, Ramsay Domloge <[email protected]> wrote: > Right, I appreciate that Services should not be able to stop 3rd Party > Activities, unrestricted. > > But what about 3rd Party Activities which they (or an intermediary Activity) > started? > > Are you saying that my Service should not be allowed to start an Activity > which, in turn, starts (and then stops) a 3rd Party Activity? > > If so, why? If an Activity can start (and then stop) a 3rd Party Activity > using finishActivity(code), then what difference does it make if the > Activity was started by a Service, rather than a User?
OK, I'll buy your basic argument. If I had to guess, this is a task problem, but it's only a guess. I poked around the source code and couldn't really narrow down where finishActivity() would determine what exactly it is finishing, or not finishing, as the case may be. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Warescription: Three Android Books, Plus Updates, One Low Price! -- 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
