> Is there a particular reason why you are calling
> getApplicationContext().getResources(), rather than just
> getResources()? getResources() is available on Service as well.
I honestly don't know/remember why.... Let me turn the question
around, why are you using getApplicationContext()?
For example, your sendWakefulWork() looks like this, why?
public static void sendWakefulWork(Context ctxt, Intent i)
{
getLock(ctxt.getApplicationContext()).acquire();
ctxt.startService(i);
}
I find the regular Context vs. ApplicationContext probably the most
confusing aspect of Android, especially the application context is not
a proper interface/class, so you cannot make it required. I think
this decision by the API design team is causing a lot of headaches for
people.
>
> --
> Mark Murphy (a Commons
> Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy
>
> Android Training in DC:http://marakana.com/training/android/
--
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
