Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>EDIT:</p> <p>Given your explanation in the comments, I think that the best approach to this would be using notifications. That is:</p> <ol> <li><p>when the "goHome" button is pressed in one sub-app controller, a notification is posted;</p></li> <li><p>the app list controller is registered to handle that kind of notifications, so it is notified when the button is pressed and can do what required.</p></li> </ol> <p>This would look like this, more or less:</p> <ol> <li><p>In your sub-app controller:</p> <pre><code>- (void) goHome: (id)sender { NSNotificationCenter *notificationCenter = [NSNotificationCenter defaultCenter]; [notificationCenter postNotificationName:@"GOHOMEPRESSED" object:nil userInfo:nil]; } </code></pre></li> <li><p>In your app list controller:</p> <pre><code>- (void)viewDidLoad { ... [[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(goHome) name:@"GOHOMEPRESSED" object:nil]; ... } - (void)goHome { [self dismissViewControllerAnimated:YES completion:NULL]; } </code></pre></li> </ol> <p>You can change the notification name used, of course (@"GOHOMEPRESSED") provided you use it consistently.</p> <p>Don't forget to remove the observer in your app list controller's <code>dealloc</code> method (I leave this to you).</p> <p>Also, try to get the logics behind this:</p> <ol> <li><p>from a given controller you present a second controller (<code>presentViewController:Volumesapp</code>);</p></li> <li><p>this will bring you altogether outside of the controller hierarchy where you were before (in your case, the tab bar);</p></li> <li><p>when you are done with the presented controller, you must call <code>dismiss</code> on the presenting controller (the step done in 2/goHome), to get back (sort of) to where you were.</p></li> </ol> <p>Hope this helps.</p> <p>OLD ANSWER:</p> <p>If I understand correctly what you are trying to do, what you need is selecting the right sub-controller inside of your tab bar controller by using <code>setSelectedIndex</code>; something like this should work:</p> <pre><code>- (void) goHome: (id)sender { [self.tabBarController setSelectedIndex:2]; } </code></pre> <p>Your current solution will simply overlap your current controller with a new controller instance presented modally. So, you are not properly going to the first scene, to use your wording, your are altogether instantiating a new scene on top of the existing one.</p>
    singulars
    1. This table or related slice is empty.
    1. POMaking a button go to 2nd tabbed scene rather than 1st?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USsergio
    1. USsergio
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMaking a button go to 2nd tabbed scene rather than 1st?
      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 a lot for your help. Did you mean to replace everything in my 'goHome' with your one line? If so, it doesn't work. Pressing the UIButton for 'goHome' does nothing. Just stays on the same screen.
      singulars
      1. PO
      1. USIainGM
    2. COCheck your `self.tabBarController` in `goHome` -- I assume it is nil. If it is, then there may be something you are not explaining about your app, since a view controller which is embedded in a tab bar controller has a non-nil `tabBarController`. Another possibility is that I am not understanding correctly how your app works and where the button that you tap is located... my understanding is that `goHome` belongs to one of the view controllers embedded in the tab bar controller...
      singulars
      1. PO
      1. USsergio
    3. COsergio, thanks for your patience and contributions here. I have never used a Tab Bar Controller before, and I am (obviously!) struggling here.Let me try to explain a bit better. Before I tried to do anything with Tab Bar Controllers, I had an app that had an initial screen showing a scrolling list of 20 'sub' apps, each with their own storyboard, .h and .m files. Each app was selectable from the first screen, and also each one had a button that ran 'goHome' (as originally posted). When that button was tapped, the user was taken back to the first screen, i.e. the list of apps. (continued below)
      singulars
      1. PO
      1. USIainGM
 

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