Note that there are some explanatory texts on larger screens.

plurals
  1. POswitch to a new activity, instead of switching fragments, when jfeinstein10's slidingmenu list item is clicked
    text
    copied!<p>I have seen a few questions raised on this topic (for e.g.: <a href="https://github.com/jfeinstein10/SlidingMenu/issues/5" rel="noreferrer">https://github.com/jfeinstein10/SlidingMenu/issues/5</a>) but I am still unclear. I hope somebody can clarify this.</p> <p>Context:</p> <p>See <a href="https://github.com/jfeinstein10/SlidingMenu" rel="noreferrer">https://github.com/jfeinstein10/SlidingMenu</a></p> <p>I have an android app that organizes screens by activities and fragments (i.e.) each screen is an activity containing one or more fragments. The new requirement is to add a sliding menu (similar to what this library provides).</p> <p>Issue:</p> <p>It appears from the examples and discussion that the right model would be to have just 1 MAIN ACTIVITY that will then switch in/out fragments belonging to the different screens. In fact the author mentions in the above thread: "If you were to launch Activities based upon the list selection, then you would not have the behavior where you swap the views that you're talking about. " and also "You can't put an Activity into the above view. That doesn't really make sense when you think about what an Activity is. ". </p> <p>Why doesn't it make sense? Obviously, I am missing the point here.</p> <p>Question:</p> <p>Given that my project already contains multiple activities (one corresponding to each screen), is my only option then to re-organize the project to have JUST 1 MAIN ACTIVITY, in order to use this library? Or alternatively, is there any way to launch a new activity when a list item in the sliding menu is clicked, and still observe the sliding menu behavior, [<strong>EDIT</strong>- added the last part to be more clear] or in other words, on how exactly to use this library within my existing app design. </p> <p>Thanks in advance</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload