Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The <code>– setToolbarItems</code> method is a UIViewController method specific to each child view controller of your navigation controller. Assuming <code>[self navigateToCommentScreen:shouldAddNewComment]</code> pushes a new view controller onto the navigation stack you will have to set the toolbar items for the new view controller too as a separate call, regardless of what the action sheet is doing. For example, </p> <pre><code>-(void) navigateToCommentScreen:(bool) shouldAddComment{ CommentViewController* viewController = [[CommentViewController alloc] init]; [self.navigationController pushViewController:viewController animated:YES]; [viewController setToolbarItems:self.toolbarItems]; } </code></pre> <p>Otherwise the new view controller will have no toolbar items and the toolbar will be blank.</p> <p><strong>Edit</strong></p> <p>I created a navigation controller with a root view controller that has a toolbar with a UISegmented control. I pushed a new view controller onto the navigation stack via a UIActionSheet delegate method and then popped it back. The toolbar was exactly how it should be on the root view controller (the segmented control faded back in as expected). You must be doing something more complicated with your controller with regards to setting the toolbar items that is causing them to disappear. Without seeing your viewController's source methods it's hard to tell what the problem is. Make sure that you are not setting your toolbar items to nil or resetting them with an empty array somehow.</p>
    singulars
    1. This table or related slice is empty.
    1. PONavigation controllers toolbar goes blank after showing a UIActionSheet from it
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USLOP_Luke
    1. USLOP_Luke
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    1. COYou are correct, but that is not the problem here. There are other places where [self navigateToCommentScreen:shouldAddNewComment]; gets called that does not cause this problem. It is only after the action sheet have been shown that the problem arise. The problem is even then when I pop ViewControllers from the navigationController. These forms calls setToolbarItems in their different viewDidLoad.
      singulars
      1. PO
      1. USnj.
    2. COSo what is the expected behavior? If you show an action sheet from a navigation controller's toolbar, the toolbar will be covered by the action sheet. Is that what you're saying the problem is? Because I don't think there's a way to show the action sheet from the top of the toolbar (having the toolbar remain visible under the action sheet). Also, viewDidLoad is not called when you pop a view controller from the navigation stack. If you need to change the toolbar items of the underlying view controller when you pop from the stack, those changes should be in viewWillAppear, not viewDidLoad.
      singulars
      1. PO
      1. USLOP_Luke
    3. COI've added more info to the question. I think I've answered all your questions there. Otherwise, please let me know!
      singulars
      1. PO
      1. USnj.
 

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