StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20017583
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-16T10:58:08.313
FavoriteCount
0
LastActivityDate
2014-01-17T10:16:54.960
LastEditDate
2014-01-17T10:16:54.960
LastEditorUserId
465677
OwnerUserId
465677
ParentId
20017026
PostTypeId
2
Score
46
ViewCount
0
LastEditorDisplayName
text
Body
"Passing data to the destination Controller" when a segue is triggered will be achieved by overriding method <code>prepareForSegue:sender:</code>. Generally, you pass data and NOT the source view controller, to the destination view controller. "data" may be a certain aspect of your application "model". It's an object like "User", or perhaps an array containing "User", etc. The destination view controller shall not have any knowledge of the source view controller. That means, the destination view controller does not need to import the header of the source view controller. On the other hand, the source view controller may have knowledge of the concrete class of the destination view controller or a base class of the destination view controller, and thus will import the header of the destination view controller. See: <a href="https://developer.apple.com/library/ios/featuredarticles/ViewControllerPGforiPhoneOS/ManagingDataFlowBetweenViewControllers/ManagingDataFlowBetweenViewControllers.html#//apple_ref/doc/uid/TP40007457-CH8-SW4">Configuring the Destination Controller When a Segue is Triggered</a> If you need some sort of "communication protocol" between the source and the destination, you might employ Delegation to communicate with other view controllers. This involves the definition of a @protocol (e.g. having a method <code>doneButton</code>) and a property <code>delegate</code> which is defined in the destination view controller. The protocol should be defined in the header of the destination view controller, if it's specific to the destination view controller. Usually, you define tho protocol from the view point of the destination controller, and not from the requirements of the source controller. The source view controller then creates a delegate (unless, it itself is it already) and sets the <code>delegate</code> of of the destination view controller. The destination view controller will send the delegate methods to the delegate, and the delegate handles it. Now, passing "data" from a VC_A to VC_B should be straight forward. You should read a few examples which use <code>prepareForSegue:sender:</code>. For example, the destination view controller may have a property <code>data</code> which represents the thing it should display. The source view controller must set this property in <code>prepareForSegue:sender:</code>. Passing data from VC_A over VC_B to VC_C should be straight forward as well. Note: Each view controller may tailor (separate, modify, prepare, slice, transform, etc.) its <code>data</code> to make it a suitable <code>data</code> for the next view controller. <hr> If VC_C needs data that is not available in its source view controller VC_B, then there are a couple of approaches to solve this. However, this is usually a sign of bad design. You could have an application model, which is global. Suppose, your "application model" is an object of type <code>Document</code>. Suppose, at any time there is only one instance of that application model. Then, the model is a "Singleton", which could be accessed from anywhere in your app like so: <pre><code>Document* document = [Document sharedDocument]; </code></pre> However, the preferred way to get an instance of a model is in the first view controller which requires access to it, in this case: VC_A. Then, VC_A passes a <code>Document</code> instance to the next view controller VC_B. And VC_B passes the document object to VC_C. You should read the official documentation "<a href="https://developer.apple.com/library/ios/featuredarticles/ViewControllerPGforiPhoneOS/Introduction/Introduction.html">View Controller Programming Guide for iOS</a>". <hr> <h3>Example 1</h3> Suppose, you have a list "Users". The list should be displayed in a table view controller, and there should also be a detail view, showing details of one User. The table view controller will have a "data" property <code>users</code>: In UsersTableViewController.h: <pre><code>@interface UsersTableViewController : UIViewController @property (nonatomic, readonly) NSArray* users; @end </code></pre> (Strictly, this <code>user</code> property doesn't need to be public. For example, if the table view internally obtains the list of users itself, there is not need to access it from outside. The "users" array is the data of the table view which shall be displayed in rows. Each row shows a "summary" of a user. More details of a user should be displayed in a detail view controller. The detail view controller's data is a single user of type <code>User</code>. When the user tabs a certain row in the table view, the detail view controller will be displayed. Before it will be displayed, the table view controller must configure the detail view controller: the table view controller assigns the detail view controller's "data property" the current selected user. Thus, the detail view controller should have a public property <code>user</code>: <pre><code>@interface UserViewController : UIViewController @property (nonatomic) User* user; @end </code></pre> The table view controller configures the detail view controller in <code>prepareForSegue:sender:</code>: In UsersTableViewController.m <pre><code>- (void) prepareForSegue:(UIStoryboardSegue *)segue sender:(id)sender { if ([[segue identifier] isEqualToString:@"ShowUserDetails"]) { UserViewController* userViewController = [segue destinationViewController]; userViewController.user = [self.users objectInListAtIndex:[self.tableView indexPathForSelectedRow].row]; } } </code></pre> <hr> <h3>Example 2</h3> The second example is more complex and uses "Delegation" as a means to establish a communication between controllers. Caution: <blockquote> This is not a complete example. The purpose of this example shall demonstrate how to use "Delegation". A full featured implementation of data tasks as shown in the example will require significant more effort. In this scenarios like these, "Delegation" will be the most preferred approach to accomplish this (IMHO). </blockquote> Suppose we want to <ul> <li>Show a User</li> <li>Modify (edit) a User </li> <li>Create New a User, and </li> <li>Delete a User</li> </ul> from within the detail view. These "data tasks" shall not be performed by the detail view controller itself, instead a delegate is responsible for these data tasks. These data actions shall be handled by the delegate: <pre><code>@protocol UserDataSourceDelegateProtocol <NSObject> - (User*) viewControllerUser:(UserViewControllerBase*)viewController; - (void) viewController:(UserViewControllerBase*)viewController dismissWithUpdatedUser:(User*)user; - (void) viewController:(UserViewControllerBase*)viewController dismissWithDeletedUser:(User*)user; - (void) viewController:(UserViewControllerBase*)viewController dismissWithCreatedUser:(User*)user; @end </code></pre> This protocol reflects the basic CRUD methods (Create, Read, Update, Delete). Again, we don't want the Detail View Controller itself to perform these data methods, but instead this will be performed by an instance implementing the <code>UserDataSourceDelegateProtocol</code>. The detail view controller has a property of this delegate, and it sends these "data tasks" to the delegate. There may be several detail view controllers, all subclasses of abstract class <code>UserViewControllerBase</code> which handle the show, edit and create tasks. Deletion of a user can be performed in the table view and in the "Show User" view controller: <ul> <li><code>ShowUserViewController</code></li> <li><code>EditUserViewController</code></li> <li><code>NewUserViewController</code></li> </ul> For example The <code>EditUserViewController</code> will send <code>viewController:dismissWithUpdatedUser:</code> when the user tabs the "back" button AND if the user has modified the user object. Now, the delegate may or may not allow to dismiss the detail view. It may disallow it when there are validation errors for example. The <code>UserDataSourceDelegateProtocol</code> protocol may be implemented in the root view controller, the table view controller for example. However, a separate class whose sole responsibility is to handle data tasks may be more appropriate. In the sample below, the table view controller will also be this data handler. The <code>UserDataSourceDelegateProtocol</code> may be defined in an extra header. In UsersTableViewController.m: <pre><code>#import "UserDataSourceDelegateProtocol.h" #import "ShowUserViewController.h" @interface UsersTableViewController () <UserDataSourceDelegateProtocol> @property (nonatomic, readonly) NSArray* users; @end // This delegate will be called when the detail view controller request // the user object which shall be displayed. - (User*) viewControllerUser:(UserViewControllerBase*)viewController { return [self.users objectInListAtIndex:[self.tableView indexPathForSelectedRow].row]; } </code></pre> Here, the Table View Controller configures the Show User Detail View Controller: <pre><code>- (void)prepareForSegue:(UIStoryboardSegue *)segue sender:(id)sender { if ([segue.identifier isEqualToString:UserShowSegueID]) { ShowUserViewController* showViewController = segue.destinationViewController; showViewController.delegate = self; // Data Source Handler is self } } </code></pre> The "Edit User" view controller is usually a destination view controller of the "Show User" view controller, which gets viewed when the user tabs the "Edit" button. The "Show User" view controller will setup the delegate for the "Edit User" view controller gets the same delegate: In ShowUserViewController.m <pre><code>- (void)prepareForSegue:(UIStoryboardSegue *)segue sender:(id)sender { if ([segue.identifier isEqualToString:UserEditSegueID]) { EditUserViewController* editViewController = segue.destinationViewController; editViewController.delegate = self.delegate; // pass through the data source hanlder } } </code></pre> The data delegate may handle an updated user as follows: In UsersTableViewController.m: <pre><code>- (void) viewController:(UserViewControllerBase*)viewController dismissWithUpdatedUser:(User*)user { if (/* is valid user and can be saved */) { [viewController.presentingViewController dismissViewControllerAnimated:YES completion:nil]; } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPassing data between View Controllers using Segue
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCouchDeveloper
UserOwnerUserId
1. USCouchDeveloper
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPassing data between View Controllers using Segue
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.