Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>that's a very general question. you're basically asking how to pass information from one controller to another controller. There are different ways to do that, a protocol (what a delegate generally communicates through) is one of them. The quickest thing you can do w/o making assumptions in your code that may be problematic later would be to pass the homeScreenController along as you push <code>messageListController</code> and then <code>detailMessageController</code>. You'll need to define an iVar and property in <code>messageListController</code> and <code>detailMessageController</code> to do this.</p> <p>Something like:</p> <p>in <code>messageListController.h</code>:</p> <pre><code>#import "HomeScreenController.h" @interface messageListController : UITableViewController { // your iVars HomeScreenController *homeScreenController; @end @property (nonatomic, assign) HomeScreenController * homeScreenController; </code></pre> <p>add the same iVar and property for <code>homeScreenController</code> to <code>detailMessageController</code>.</p> <p>in <code>homeScreenController.h</code>:</p> <pre><code>- (void)pushMessageListController { MessageListController *messageListController = [[MessageListController alloc] init]; messageListController.homeScreenController = self; // push messageListController onto navigation controller here [messageListController release]; } </code></pre> <p>in <code>messageListController</code> do the same thing as above when creating and pushing <code>detailMessageController</code>. Now, in <code>detailMessageController</code> you can send messages directly to <code>homeScreenController</code>.</p> <p>If you want to generalize the above implementation so your controllers aren't specifically knowledgeable about each other then you can define a protocol and pass <code>homeScreenController</code> through as a delegate supporting that protocol.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to delegate back to the previous veiwcontroller
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USXJones
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to delegate back to the previous veiwcontroller
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COthanks for the detailed explanaion. is this what is should be doing in when i push detailview. please correct me if i am wrong. - (void)pushDetailMessageController { DetailMessagetController *detailmessage = [[DetailMessagetController alloc] init]; detailmessage.delegate = self; // push messageListController onto navigation controller here [detail release]; }
      singulars
      1. PO
      1. USRajashekar
    2. CONo, my example did not use a protocol or define a `delegate` iVar & property. If you use my example, to push a `detailViewController` you would do the same thing I did when pushing the `messageListController`. After alloc/init, set it's `homeScreenController` property to the `homeScreenController` instance that was passed in to `messageListController`.
      singulars
      1. PO
      1. USXJones
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload