dagger-2

问题 I am currently trying to implement the MVP pattern on Android. However, I came to think about memory leaks (since the presenter holds a reference to the activity - the view). My question is, should I set the view of the presenter to null say onDestroy of the activity? This is my main activity: public class MainActivity extends AppCompatActivity implements MainView { private Button loadUser; private TextView mTextView; @Inject IMainPresenter mPresenter; @Override protected void onCreate(Bundle

问题 I am currently trying to implement the MVP pattern on Android. However, I came to think about memory leaks (since the presenter holds a reference to the activity - the view). My question is, should I set the view of the presenter to null say onDestroy of the activity? This is my main activity: public class MainActivity extends AppCompatActivity implements MainView { private Button loadUser; private TextView mTextView; @Inject IMainPresenter mPresenter; @Override protected void onCreate(Bundle

问题 I have moduleA setup as an application wide singleton provider, ModuleB as a user related object provider My user display fragment will use system wide bus to send message to others and use user related object to display. Problem cannot inject different scrope class into one object. Use component.getX method works fine, but inject is prefered way. Error message: @UserScope may not reference bindings with difference scopes: @Provides @Singleton Bus ModuleA.provideBus() @Module public class

问题 I'm trying to use dagger 2 on my Android application to inject the new ViewModel from arch android library. From what I see on this sample https://github.com/googlesamples/android-architecture-components/tree/e33782ba54ebe87f7e21e03542230695bc893818/GithubBrowserSample I need to use this: @MustBeDocumented @Target(AnnotationTarget.FUNCTION, AnnotationTarget.CONSTRUCTOR, AnnotationTarget.PROPERTY_GETTER, AnnotationTarget.PROPERTY_SETTER) @Retention(AnnotationRetention.RUNTIME) @MapKey internal

问题 I'm trying to use dagger 2 on my Android application to inject the new ViewModel from arch android library. From what I see on this sample https://github.com/googlesamples/android-architecture-components/tree/e33782ba54ebe87f7e21e03542230695bc893818/GithubBrowserSample I need to use this: @MustBeDocumented @Target(AnnotationTarget.FUNCTION, AnnotationTarget.CONSTRUCTOR, AnnotationTarget.PROPERTY_GETTER, AnnotationTarget.PROPERTY_SETTER) @Retention(AnnotationRetention.RUNTIME) @MapKey internal

问题 I have a custom view extending a TextView . Where should I call my component to inject the view? component.inject(customTextView); 回答1: So, I've find out that I need to add the injection in the constructor of my custom view (in all of them, or make one call the other) Example: public class CustomTextView extends TextView { @Inject AnyProvider anyProvider; public CustomTextView(Context context) { this(context, null); } public CustomTextView(Context AttributeSet attrs) { super(context, attrs);

问题 I have a custom view extending a TextView . Where should I call my component to inject the view? component.inject(customTextView); 回答1: So, I've find out that I need to add the injection in the constructor of my custom view (in all of them, or make one call the other) Example: public class CustomTextView extends TextView { @Inject AnyProvider anyProvider; public CustomTextView(Context context) { this(context, null); } public CustomTextView(Context AttributeSet attrs) { super(context, attrs);

问题 Recent after update Android Studio (2.0.7) (maybe this is the cause) sometimes when building i get that error. Idea is that usually compilation goes well but sometimes I get dagger error. Is possible that is problem in Dagger configuration? Error itself: Executing tasks: [:app:assembleDebug] Configuration on demand is an incubating feature. Incremental java compilation is an incubating feature. :app:preBuild UP-TO-DATE :app:preDebugBuild UP-TO-DATE :app:checkDebugManifest :app:preReleaseBuild

问题 Recent after update Android Studio (2.0.7) (maybe this is the cause) sometimes when building i get that error. Idea is that usually compilation goes well but sometimes I get dagger error. Is possible that is problem in Dagger configuration? Error itself: Executing tasks: [:app:assembleDebug] Configuration on demand is an incubating feature. Incremental java compilation is an incubating feature. :app:preBuild UP-TO-DATE :app:preDebugBuild UP-TO-DATE :app:checkDebugManifest :app:preReleaseBuild

问题 I have a class which gets arguments in a constructor: public class Dependency{ Dependency(int number1, int number2, int number3, DependencyListener listener){} } each dependent class needs to path different arguments in order to instantiate a dependency. How should i define the module and the component that other classes could initiate it properly while transferring different values and passing 'this' as the listener? Also, How should i use the @Inject method in this case? Edit 1 @jeff-bowman