Difficult is a poor choice of words. I'm just curious what the design discussion was like with not making Application Context consistently accessible from any point in code. Was it a security issue? Memory leaks? Especially when we have something like Toasts which can be called from any level of context but requires an application context to function in all situations.
Feel like I'm missing something but couldn't find anything in my limited research regarding context scopes. On Wednesday, July 16, 2014 4:11:39 PM UTC-7, TreKing wrote: > > > On Wed, Jul 16, 2014 at 5:46 PM, peter <[email protected] <javascript:>> > wrote: > >> I guess a better way to phrase my question: >> Is Application always accessible as a singleton? >> > > Should be. > > >> If it is what was the reasoning of making it difficult to reach from >> other contexts? >> > > What is difficult about Context.getApplicationContext()? > > > ------------------------------------------------------------------------------------------------- > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > transit tracking app for Android-powered devices > -- 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/d/optout.
