Thanks guys, I guess from what I read that the way I have it (much like MB's suggestion) is probably the best. It just seems weird with all the activity destroying and recreating that is going on and causing minor issues. Is there a way to keep my main activity alive while they login? Its a separate activity not a popup dialog.
--G On Jul 20, 7:24 pm, MB <[email protected]> wrote: > Why don't you do this? > > MainActivity > In OnCreate. > if(userloggedon) > showLoggedOnView > else > showLoginScreenView > > --MB. > > On Jul 17, 10:11 am,Gaelin<[email protected]> wrote: > > > First I have my app running currently and its working fine, I just > > question how I implemented it. I come from a linear C++ background > > and this Activity/Intent thing is a little new to me. Here is how my > > app works currently (order of activities started) ("->" = Starts > > Activity, "<-" = Returns from activity) > > > MainActivity > > -> Login Activity > > <- onActivityResult > > function displayListOfItems > > ... > > > I am wondering if I should switch the starting intent as follows: > > > LoginActivity > > MainActivity > > function displayListOfItems > > ... > > > The issue I had with the second scenario was that pressing the back > > hard key would take me from the MainActivity back to the LoginActivity > > and I didn't like this. I guess to sum up my question, is it normal > > for the MainActivity to handle all subsequent starting of activities > > or is it common to do a more linear implementation? > > > --G -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
