6

My problem seems like a generic problem, yet can't seem to find an answer for it.

I have a situation where when the user taps on a custom UITableViewCell, I would like to display an alert and then based on the response to the alert, either stay on the same view (user selecting cancel) or display another view (if the user selects proceed). And I would like to do this using the storyboard feature & segues.

How would one go about this? Do you have to do this the old fashioned way?

abu.marcose
  • 550
  • 2
  • 8
  • 20

3 Answers3

11

@user, Just create the alertView the old fashion way; I do know of any storyboard feature to do this differently. Where storyboard can help is with the segues. You can call the segues programmatically. With you alert view cancel button you can just return (i.e. do nothing). For the other option, to display another view, you can programmatically call a segue to transition to the desired view. If you don't have the proper segue already defined for some other reason on your storyboard, just create a button out and use that to create the segue and name it. Name the segue by clicking on it in storyboard and use the attributes inspector to give it name (identifier). Then hide the button or put it out of the view. I typically put these type of button on the toolbar and use spacers to keep them out of the view. Here's some sample code:

Call the segue from the alert view delegate like this:

[self performSegueWithIdentifier: @"done" sender: self];

Also implement this method to do any necessary task to prepare for the segue:

- (void)prepareForSegue:(UIStoryboardSegue *)segue sender:(id)sender
{
if ([[segue identifier] isEqualToString:@"done"]) 
    {
        //    [[segue destinationViewController] setManagedObjectContext:self.managedObjectContext];
        //    [[segue destinationViewController] setSelectedClient:selectedClient];
    }
}
T.J.
  • 3,942
  • 2
  • 32
  • 40
  • 1
    that's what I have done; just seemed like such a hack, i figured there was a more obvious way that I had overlooked. – abu.marcose Dec 17 '11 at 19:31
  • 1
    @user, if you or anyone else reading this discovers a better way place let us know. – T.J. Dec 17 '11 at 20:54
8

You can create segues directly from the startingViewController to multiple destinationViewControllers that can then be "performed" programmatically. You do not need to create any hidden buttons for them, which does seem like a hack.

DataJock
  • 226
  • 2
  • 6
  • +1, but how do you create segues directly from the startingViewController to multiple destinationViewControllers? Do you mean just Ctrl-drag between view controllers, and naming the segues? – brainjam Jan 03 '12 at 21:21
  • 1
    Yes, I did mean that you just Ctrl-drag between the view controllers. The main point being that you don't select an element of the view controller inside a storyboard view, but you select the actual view controller itself and Ctrl-drag to the other views from it. I have done this myself and it worked nicely. – DataJock Jan 04 '12 at 01:50
  • Nice! No more phantom buttons for me. – T.J. Jan 20 '12 at 14:14
  • 3
    Obviously you'd do it this way if you can connect the two view controllers. The reason for using phantom buttons is that sometimes you want to create a segue from a view controller to itself, which Xcode doesn't seem to let you do. – houbysoft May 30 '12 at 19:25
4

OK I came up with a solution in keeping with the storyboard that I like.

Example:

My tableview has 2 sections, grouped, and cells are dynamic prototype. Section 0 contains one row/UITableViewCell & I don't want it to segue. Section 1 contains multiple cells that I want to trigger the segue & drill down into the detail.

In Storyboard:

  • I removed the segue linking the tableviewcell to the destination view controller.
  • I made a 'generic' segue linking the source view controller directly to the destination view controller.
  • In the attributes on the segue, I set the identifier ('EditTimePeriod') and set the type to Push (I presume Modal would work just the same).

In the source view controller:

  • In the prepareForSegue method I handled both the common 'AddTimePeriod' segue I control-dragged from my UIBarButtonItem (Add), along with the 'generic'(vc-->vc) 'EditTimePeriod' segue.

    - (void)prepareForSegue:(UIStoryboardSegue *)segue sender:(id)sender {

    // handle the click of the 'Add' bar button item    
    if([segue.identifier isEqualToString:@"AddTimePeriod"]) {
        TimePeriodViewController* tpvc = (TimePeriodViewController*)segue.destinationViewController;
        tpvc.delegate = self;
        // database & entity stuff for adding the new one to the mOC, etc
    }

    // handle the click of one of the 'editable' cells - 
    if([segue.identifier isEqualToString:@"EditTimePeriod"]) {
        TimePeriodViewController* tpvc = (TimePeriodViewController*)segue.destinationViewController;
        tpvc.delegate = self;
        TimePeriod * newTP = [self.timePeriodArray objectAtIndex:self.tableView.indexPathForSelectedRow.row];
        tpvc.timePeriod = newTP;
    }
}

  • Then I implemented the tableView:didSelectRowAtIndexPath method, and put my condition in here. If the selected row was outside of section zero I called the EditTimePeriod segue manually, defining the sender as the selected tableviewcell:

    - (void)tableView:(UITableView *)tableView didSelectRowAtIndexPath:(NSIndexPath *)indexPath {

    if(self.tableView.indexPathForSelectedRow.section!=0){
        [self performSegueWithIdentifier:@"EditTimePeriod" sender:[tableView cellForRowAtIndexPath:indexPath]];
    }

    [self.tableView deselectRowAtIndexPath:indexPath animated:YES];

    return;    
}

would be nice to code the cell in section 0 so that it is not selectable in the first place! Hope this helps though.

** and then 5 minutes later I took another look and realized I could just move the data from section 0 into the section header, which is more intuitive and wasn't being used anyway. leaving the design open for a standard segue from each tableviewcell without needing any condition/check. Was a good exercise anyway though :)

cafeakashic
  • 41
  • 3