> > Activities and Services both inherit from Context so you wouldn't need to > use your global_context in those cases either. In what situations are you > running into that you are using this global_context and don't have access > to it through another way? >
Same thing here as with views... You should not be passing around these contexts to things that will outlast the activity or service. Thanks, Justin Anderson MagouyaWare Developer http://sites.google.com/site/magouyaware On Tue, Aug 28, 2012 at 3:19 PM, Justin Anderson <magouyaw...@gmail.com>wrote: > To load assets or resources you need to use the Application context... >> > > I read that and realized this was wrong... I meant to say that as long as > you are only loading assets or resources then you would be perfectly fine > using the application context (but you don't need to if you have another > way to get a context). The application context should not be used for > anything having to do with UI. > > > Thanks, > Justin Anderson > MagouyaWare Developer > http://sites.google.com/site/magouyaware > > > On Tue, Aug 28, 2012 at 3:14 PM, Justin Anderson <magouyaw...@gmail.com>wrote: > >> To load assets or resources you need to use the Application context... > > > -- 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 android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
