Startup/Splash Screen: Best Practice ?

Discussion in 'iOS Programming' started by Fontano, Oct 15, 2008.

  1. Fontano macrumors member

    Joined:
    Jun 27, 2008
    #1
    Here is the program flow that I want to do:

    Application Starts:
    -) A Startup Screen appears, that has a logo and a progress indicator.
    This view/screen will then proceeded to check for user settings, check for network connection, and some other tasks.

    -) If this is a first time load, it will then send the user to a setup screen
    -) If is not, and there are no issues with the startup, it will send them to the main menu.

    That is the program flow (up till the MainMenu).

    What I have kinda working now is:
    From the NavigationBar template, I have the splash screen (hidden nav bar).
    It then does our startup and process steps in a seperate thread, so the progress indicator can spin.

    It then pushes onto the NavController, the next appropriate viewcontroller.

    Here is where I have the problem.
    At this point, I don't want the "BACK" button, to take me back to the startup screen/viewcontroller.

    I tried the POP options on the navigation controller, that doesn't work (at least it didn't for a quick test).

    So is there a better way to do what I want? (Basically when it gets to the main menu, that the navigation path is cleared and the main menu is the root).

    Thanks
     
  2. firewood macrumors 604

    Joined:
    Jul 29, 2003
    Location:
    Silicon Valley
    #2
    Why are you pushing the start-up view if you never want to go back to it? There are (many) other ways of switching views.


    .
     
  3. Fontano thread starter macrumors member

    Joined:
    Jun 27, 2008
    #3
    I'll admit, it is most probably because I don't have 100% understanding of how this all snaps together. I am getting a pretty good understanding of it, and progressing nicely.

    But there are times that I do something in a way that works, that may not be the right. Hence this case.

    I started with the base template, with the navigation control.
    What ultimately I want though, is my navigation control not to really start until the MainMenu segment of the application.

    So now that I look at it, with another comment in the knowledge base of my head (thank you for that).

    I shouldn't be using the Navigation Controller in my first splash/setup screen, and then introduce the navigation controller when I get to the main menu (because from there on out, I will be using the navigation controller)

    I guess I need to do some reading on how to go from a view on a window, to another View in a seperate NIB file, with the same right to left transition that I get from pushing the NIB file on the navigation controller.
     

Share This Page