StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
383713
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-12-20T20:38:08.467
FavoriteCount
0
LastActivityDate
2008-12-20T20:38:08.467
LastEditDate
LastEditorUserId
0
OwnerUserId
41497
ParentId
350645
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
It's not obvious from the question if you're creating a custom UIDatePicker subclass, or if you are just implementing UIDatePicker delegate methods in several different custom UIViewController subclasses. In either case, I think some combination of a delegate and a protocol is what you're looking for. <blockquote> The parent controller just needs to tell the child controller who they are, by passing self in to some child controller instance variable </blockquote> This is exactly what a delegate is useful for. Declare it in your Objective-C class as type id. You can make it a property if you like using the usual symantics. <pre><code>id delegate; </code></pre> Now, to address the second concern: <blockquote> The problem with that is, the child controller cannot access methods/instance variables of the parent without importing the class's interface file </blockquote> You definitely don't want to access ivars directly, and in Objective-C, you can always send any message to any object (you'll get a compiler warning, but it is not an error). There is a way to get rid of those warnings though, called Protocols. A protocol is like a Java interface; it lets you define a list of methods, and classes can declare that they implement the protocol. The syntax for creating a protocol looks like this: <pre><code>@protocol ProtocolName - (void)sometMethod; @end </code></pre> When you declare your class, you say it implements a protocol like this: <pre><code>@interface MyClass <MyProtocol> </code></pre> Use a comma separated list to implement multiple protocols. The last trick you'll want to know is how to define a pointer that requires the asignee implement a specific protocol. Going back to our delegate implementation before, we can add the same angle bracket syntax, which tells the compiler that we expect the object we're assigning to implement this protocol. <pre><code>id<MyProtocol> delegate; </code></pre> You can declare the protocol in its own file, and you need only to import that protocol file in any class that uses the protocol. You can also use this in combination with August's suggestion above, and implement the common functionality in a common base controller object, having each custom controller subclass that base. (another overview of protocols: <a href="http://en.wikipedia.org/wiki/Objective-C#Protocols" rel="nofollow noreferrer">http://en.wikipedia.org/wiki/Objective-C#Protocols</a>)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POOne Date Picker UIViewController for all Parent Controllers
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USRoss Boucher
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. 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
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.