StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9274666
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-02-14T09:42:39.243
FavoriteCount
0
LastActivityDate
2012-02-14T09:42:39.243
LastEditDate
LastEditorUserId
0
OwnerUserId
268317
ParentId
9274376
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
You should set your AViewController as the delegate of your BViewController so you can message it back after a particular event. Using a delegate will also allow better decoupling of your ViewControllers. In your BViewController, define a protocol like this : BViewController.h : <pre><code>@protocol BViewControllerDelegate <NSObject> - (void)viewB:(UIViewController *)didEnterMessage:(NSString *)message; @end </code></pre> and add a delegate property : <pre><code>@property (nonatomic, weak) id <BViewControllerDelegate> delegate; </code></pre> When the user enter the message in your BViewController and hit the button that pops the BViewController to show to AViewController do this : <pre><code>- (IBAction)messageEntered { if ([self.delegate respondsToSelector:@selector(viewB:didEnterMessage:)]) { [self.delegate viewB:self didEnterMessage:self.yourTextField.text]; } } </code></pre> Your AViewController should implement the BViewControllerDelegate protocol like this : AViewController.h : <pre><code>@interface AViewController <BViewControllerDelegate> </code></pre> When your AViewController creates the BViewController, it should set itself as its delegate before presenting it. Might look like this : <pre><code>BViewController *bvc = [[BViewController alloc] init…]; bvc.delegate = self; </code></pre> And finally, your AViewController should implement the viewB:didEnterMessage: method : <pre><code>- (void)viewB:(UIViewController *)didEnterMessage:(NSString *)message { self.myLabel.text = message; } </code></pre> That's the cleanest way to do that, IMHO.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POhow to access previous view elements in UINavigationController
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USThomas Balthazar
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POhow to access previous view elements in UINavigationController
 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
 VTAcceptedByOriginator
CommentsPostId
1. COHi Thomas. thanks for the answer. this is a good solution for the problem. however I am looking for something that can be used directly to pass the values to properties like we pass the objects when pushing a new viewcontroller. I have edited my question for better understanding. thanks.
 singulars
 PostPostId
 PO
 UserUserId
 USSam

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.