Oh, I see… So, startActivity really comes from the Context class?
I was looking at the docs for Activity, and didn't realize it was an * override*. On Monday, February 4, 2013 11:07:08 AM UTC-6, Streets Of Boston wrote: > > If you want to start one activity (screen) and report a result back to the > calling activity (screen) you need the handle of the calling activity. No > way around it. > > If you are not worried about reporting a result back, you can get hold of > the Application Context (context.getApplicationContext()), which is fixed > in your app's process. Store this Application Context in a global/static > variable and use it to start new activities. > > > > On Friday, February 1, 2013 4:22:34 PM UTC-5, bob wrote: >> >> Can someone help me understand why the startActivity method is in the >> Activity class? >> >> I really don't feel like it clearly belongs in any class. >> >> I basically want to call the function when I don't necessarily have a >> handle to an Activity object yet. >> >> -- -- 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
