Update: 06-Mar-18 Use MyApplication instance instead of Context instance. Application instance is a singleton context instance itself. public class MyApplication extends Application { private static MyApplication mContext; @Override public void onCreate() { super.onCreate(); mContext = this; } public static MyApplication getContext() { return mContext; } } Previous Answer You can get the the application context … Read more
It depends on the role of the class. But anyway pass ApplicationContext but not Activity one. If you pass Activity context gc can’t remove it from the memory when after you don’t need activity anymore. But application context is used while application was not finished by OS.Refer Avoid Memory Leaks
is it safe to save the app context to a static variable? Presently, yes, it appears to be safe, though I would not have getAppContext() return Context, but instead return App or Application. That being said, the fact that the core Android team did not set it up this way in the first place suggests … Read more
Which context to use? There are two types of Context: Application context is associated with the application and will always be the same throughout the life of application; it does not change. So if you are using Toast, you can use application context or even activity context (both) because Toast can be displayed from anywhere … Read more
@Module public class MainActivityModule { private final Context context; public MainActivityModule (Context context) { this.context = context; } @Provides //scope is not necessary for parameters stored within the module public Context context() { return context; } } @Component(modules={MainActivityModule.class}) @Singleton public interface MainActivityComponent { Context context(); void inject(MainActivity mainActivity); } And then MainActivityComponent mainActivityComponent = DaggerMainActivityComponent.builder() … Read more
You can pass the context to the non-activity class which is the preferred way or you could encapsulate the base context of the application to a singleton which would allow you to access the context anywhere within the application. At some cases this might be a good solution but in others its certainly not a … Read more
Of course, never fails. Found the solution about a minute after posting the above question… solution for those that may have had the same issue: ContextWrapper.getFilesDir() Found here.
You can do that using ContextWrapper, as described here. For example: public class MyContextWrapper extends ContextWrapper { public MyContextWrapper(Context base) { super(base); } public void makeMyAppAwesome(){ makeBaconAndEggsWithMeltedCheese(this); } } And call the non activity class like this from an Activity new MyContextWrapper(this);
Obtaining the Context in the constructor has (at least) three advantages: You only do it once, not every time, getView() is called. You can use it for other purposes too, when needed. It also works, when parent is null. However, if you don’t have any problems with your solution, you might as well stick to … Read more
First of all, let me explain what the context is a bit better, then let’s go on to how it can be used and received. Essentially, context is a reference to linking your resources to your program. Each object is given its own context, which contains the resources required to set that object up. It … Read more