Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7761893
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 1, 20262026-06-01T14:15:09+00:00 2026-06-01T14:15:09+00:00

The documentation for the toolbar property in UINavigationController says: This property contains a reference

  • 0

The documentation for the toolbar property in UINavigationController says:

This property contains a reference to the built-in toolbar managed by the navigation controller. Access to this toolbar is provided solely for clients that want to present an action sheet from the toolbar. You should not modify the UIToolbar object directly.

I can understand why I shouldn’t modify the toolbar’s visibility or items, because UINavigationController provides an interface to do that. But I’ve added a button that, when tapped, causes the toolbar to animate offscreen. Why shouldn’t I do this?

Must I instead create my own ToolbarNavigationController class that replicates everything UINavigationController does with the toolbar just sod, I can do what I want with the toolbar? Seems like a waste of effort when the UINavigationController already does what I want. Why on earth would the docs suggest I so severely limit what I do with it?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-01T14:15:10+00:00Added an answer on June 1, 2026 at 2:15 pm

    Three ways that having moved the navigation bar might confuse it:

    1. If your app can be rotated, does it stay in the right place after rotation? When it returns to the screen, does it animate on from the right place?
    2. If you display a search bar, the navigation bar animates itself off. If it’s already been moved manually, does it know where it is?
    3. If you push a viewController with hidesBottomBarWhenPushed set to YES, and return, does the navigationController put its toolbar back where it belongs?

    On the other hand, how about calling UINavigationController setNavigationBarHidden:NO animated:YES – does that do what you want, while letting the navigation controller maintain control of its toolbar?

    Edit: Sorry about misreading. Yes, you probably can do what you’re asking, as long as you don’t also do anything (like item 3 above) that mean the navigationController moves its toolbar around.

    On the other hand, the behavior you want can also be achieved as follows:

    1. For the viewController with the multiple toolbars, set its hidesBottomBarWhenPushed to YES.
    2. Place all the toolbars that viewController needs on it, and have it take full control of their positions and visibility.

    If the default toolbar has the same layout as the navigationController’s own toolbar, this will create the odd visual effect of seeing the same set of toolbar items slide off and then on again, but everything else should work.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Documentation says: The Grails team discourages the embedding of core application logic inside controllers,
Documentation says Dictionary keys order is unspecified. I guess it means the first added
Documentation says: Changes to fields of the passed entities are not recognized by the
Documentation can be found here It says in the example: onDrop: Called whenever a
my application has a UIViewController subclass which is being managed by a UINavigationController. In
Documentation says that waypoints limit is 8 points. But I have to draw a
I'm an experienced developer but a relative newbie with Cocoa. The Cocoa documentation says
I've been looking at this apple document: http://developer.apple.com/library/mac/#documentation/UserExperience/Conceptual/AppleHIGuidelines/Controls/Controls.html In the Window-Frame Controls section it
When I try to show five rows only, the paging toolbar says showing 1-5
Documentation for scala.util.Random.nextInt (n: Int): Int says "Returns a pseudorandom, uniformly distributed int value

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.