There is no current context, you need to explicitly pass it in. Having a concept of a current concept is very problematic in the face of multiple embedded activities inside of each others and thus calls going arbitrarily back and forth between them.
On Sun, Nov 30, 2008 at 12:10 PM, Peter Jeffe <[EMAIL PROTECTED]> wrote: > > I can't find any way to determine my current context, I'm hoping I'm > just missing it, but maybe I'm missing something about contexts. I > have a singleton object that maintains a connection to a service on > behalf of potentially multiple activities, and I need to be able to > bind/unbind on their behalf, and it's impractical (and maybe > impossible) to know which context I'm running under at any given > point. So I just want to be able to determine the context from down > in the call stack. Thanks for any help. > > > > -- Dianne Hackborn Android framework engineer [EMAIL PROTECTED] Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
