Angry Ninja- Rather than use the built-in start screen defined in AN_Posters.xib, I have built a another screen that will be easier for me to add additional controls and modify(USC Screen). There is a button on that screen that loads AN_Posters. However after the initial setup, I would like to go right to the storyboard rather than showing the AN_Poster screen that I replaced. I thought that I would just need to put in a line in AN_Posters.m that calls -(void)pushToStoryManually Adding "[self pushToStoryManually];" in: viewDidLoad - loops endlessly viewWillAppear - no effect Pretty sure it is a really basic code flow question, but I have not tried something like this before) Thanks

For some reason, I always have the same issue with the pushtostorymanually code from mrdavid and kittsy. It works if you put an afterDelay of 0.01 code in there, but then you see a glimpse of another screen before it pushes the new storyboard screen. That's why I do a small "landing page" that requires the user to tap something to load whatever is in the storyboard in any plugins that utilize storyboards. It's kind of a crappy work around, but the only way I've been able to get it to work. :(

Willing to try the delay and then minimize what is on the current landing page. I am trying to avoid the user hitting two buttons to get there. Where in relation to the pushtostorymanually line would I add the delay? I am not in front of Mac so could you also please show what the line of code would be? Thanks!

You guys could try calling the method on the main thread. [self performSelectorOnMainThread:@Selector(pushToStoryManually) withObject:nil]; If your project has no idea what performSelectorOnMainThread is, (which it probably doesn't, for a few reasons), go ahead and try this: dispatch_async(dispatch_get_main_queue(), ^{ [self pushToStoryManually]; }); You can read about the differences here if interested: http://blackpixel.com/blog/2013/11/performselectoronmainthread-vs-dispatch-async.html Haven't looked at my code for a while, but it's probably something noobish that I missed at the time of writing it, I did a lot of work arounds instead of fixing the problem with porting. Hope this helps. Cheers, David Van Beveren http://btmods.com/chat ^ Chat with other BT members live! http://btmods.com/hire ^ Hire MrDavid for one of his services!

Thanks! Will give it a go tonight.

Cheers :-) David Van Beveren http://btmods.com/chat ^ Chat with other BT members live! http://btmods.com/hire ^ Hire MrDavid for one of his services!

snuck some time at lunch... When I replaced the initial line: [self pushToStoryManually]; with: [self performSelectorOnMainThread:@Selector(pushToStoryManually) withObject:nil]; Thought App was aware of performSelectorOnMainThread. However build fails with unexpected "@" in program for the new line? ============= Tried alternate: dispatch_async(dispatch_get_main_queue(), ^{ [self pushToStoryManually]; }); and it worked same as : [self pushToStoryManually]; Back to square one...