You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 26, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 26, 2023. It is now read-only.
The @WindowFeature annotation create requestWindowFeature(x) in the init_() function even if the activity use the support library (instead of using supportRequestWindowFeature(x))
Ok why not. I Find out how to do it.
However, I have an issue. supportRequestWindowFeature is from ActionBarActivity and not from FragmentActivity and unfortunately there is no appcompat-v7 library on Maven central, only the v4 support library. So I can't make a
Any clues ?
This is not a problem at all. It means we cannot test it in the functional test, but we can in the compile-time test (by adding a fake ActionBarActivity). You can generate arbitrary code. :) Check out this test, which adds Fragment to the classpath. The added classes must be in src/test/resources, like this.
If you have further questions, do not hesitate to ask..
The
@WindowFeatureannotation createrequestWindowFeature(x)in theinit_()function even if the activity use the support library (instead of usingsupportRequestWindowFeature(x))