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.
The second one, for Phone, using the "android:configChanges" attribute (to avoid application restart on orientation change).
Both will share the same code, excepted the 2nd one which will handle "onConfigurationChange" by itself.
Since we can't duplicate activities in the Manifest, my plan was to extends the first one :
class MyPhoneActivity extends MyTabletActivity_ { ... }
BUT, using @EActivity on MyTabletActivity, the generated class is final!
Is there any workaround possible, that's really frustrating!
(To those asking why I'm not using the same activity for both tablets and phone : the phone activity has the same layout in both portrait and landscape, while the tablet activity have different one. Thus, application restarting is useless concerning phone. Even more considering that handling configuration change is the ONLY way to keep webviews state.)
Hi there!
For my application, I need 2 activities :
Both will share the same code, excepted the 2nd one which will handle "onConfigurationChange" by itself.
Since we can't duplicate activities in the Manifest, my plan was to extends the first one :
class MyPhoneActivity extends MyTabletActivity_ { ... }
BUT, using @EActivity on MyTabletActivity, the generated class is final!
Is there any workaround possible, that's really frustrating!
(To those asking why I'm not using the same activity for both tablets and phone : the phone activity has the same layout in both portrait and landscape, while the tablet activity have different one. Thus, application restarting is useless concerning phone. Even more considering that handling configuration change is the ONLY way to keep webviews state.)