StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16517523
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-05-13T08:16:22.093
FavoriteCount
0
LastActivityDate
2013-05-13T08:16:22.093
LastEditDate
2017-05-23T11:55:59.260
LastEditorUserId
-1
OwnerUserId
231684
ParentId
16499882
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
clankill3r, You should avoid creating singleton <code>UIViewController</code>s (see comments in this discussion <a href="https://stackoverflow.com/questions/5781749/uiviewcontroller-as-a-singleton">UIViewController as a singleton</a>). This has been also highlighted by @CarlVeazey. IMHO, you should create a <code>UIViewController</code> each time you need it. In this case your view controller would be a reusable component. When you create a new instance of your controller, just inject (though a property or in the initializer the data you are interested in, <code>suggestedRoute</code> in this case). A simple example could be the following: <pre><code>// YourViewController.h - (id)initWithSuggestedRoute:(id)theSuggestedRoute; // YourViewController.m - (id)initWithSuggestedRoute:(id)theSuggestedRoute { self = [super initWithNibName:@"YourViewController" bundle:nil]; if (self) { // set the internal suggested route, e.g. _suggestedRoute = theSuggestedRoute; // without ARC enabled _suggestedRoute = [theSuggestedRoute retain]; } return self; } - (void)viewDidLoad { [super viewDidLoad]; [self drawSuggestedRoute:[self suggestedRoute]]; } </code></pre> For further info about <code>UIViewController</code>s, I really advice to read two interesting post by @Ole Begemann. <ul> <li><a href="http://oleb.net/blog/2012/02/passing-data-between-view-controllers/" rel="nofollow noreferrer">Passing Data Between View Controllers</a></li> <li><a href="http://oleb.net/blog/2012/01/initWithNibName-bundle-breaks-encapsulation/" rel="nofollow noreferrer">initWithNibName:bundle: Breaks Encapsulation</a></li> </ul> Hope that helps.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POgetInstance before initWithNibName:
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USLorenzo B
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
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.