Can we have NavigationBar at the bottom of the screen.As i have to display a image at the top of the screen.
You can put one anywhere but the system will not manage it for you.
If you want to put a nav bar at the bottom of the screen though, the chances are great you really want to have a toolbar, or a tab bar... navigation controllers are just not good on the bottom and users will think it's really wierd.
Can't you just make the nav bar transparent and have the image go behind it?
Try using UINavigationBar's initWithFrame: to position it how you would like. You could also put it inside a view which is located below your image.
It might be worth using a toolbar instead. Users are used to seeing the navigation bar at the top. The interface guidelines might "require" this too which could lead to fun when you submit your application to Apple.
Related
I am using the XLPagerStrip pod in my current app and I would like to extend the tableviewcontroller inside my ButtonBarPagerTabStripViewController under the nav bar and have users able to see it through the text that is on button bar navigation bar. To do this usually I would make my navigation by transparent like from the examples here, however it doesn't seem to work with the ButtonBar. I am wondering if there was an easy way to do this or if this is unsupported by the library currently? Thanks!
I ended up using the link I posted above and on creation of the bar controller setting its navigation bar. This made it transparent.
I have an interesting problem. I have an app that I'm developing that involves photos so screen space is at a premium. Also, using disappearing and reappearing nav / tool bar controllers (like in the camera app) doesn't make sense for me. In a perfect world, I'd use a UITabBar to switch between the 4 main navigational view controllers that my program implements, however I also am going to need space for a toolbar right on top of the tab bar most of the time. These two components take up too much space between the two of them so I need a way to save some space.
That's where I came up with the idea of using a toolbar to implement the functionality of both the TabBar and ToolBar. On the left side of the ToolBar would be the 4 buttons that allow access to my 4 main navigational view controllers. The one that is currently on the window would have it's button depressed. Then there would be a divider, and on the right side of the tool bar would be buttons specific to whatever view is currently on the window.
Anyhow, I'm just wondering if anyone has any clever ideas on how they'd implement this?
wat do u mean by left and right of toolbar??? adding a tab bar will not affect ur view size. when adding a toolbar, well yes it does affect ur view size.
my idea wolud be add a toolbar to the top of ur view and u can make it visible only when the user taps on the screen. until then keep the toolbar hidden. when the user clicks for the second time on the screen hide ur toolbar. this way u can have the whole view for ur pics and also have a toolbar for giving options.
I want to use Tabview for my whole app. However in certain view, I have more operations than I can fit in the navigator bar. So I thought of using Toolbar but toolbar should be located at the bottom, right? Toolbar looks weird to be on top of the tabview, and hiding tabview for one view doesn't really make sense. I guess I can go with more buttons in the main view, but any other alternatives?
What can one use to add more operation(s) to tabview?
Thanks
In regards to keeping the UI simple, Apple recommends using a "More" button on the tab bar to fit additional functionality in on a tableview or some other NIB.
Additionally, you could always have another NIB that is hidden unless they hit a certain area or button and then it pops into view for controls, options, etc.
I posted earlier but am running into similar problems again. Basically the way that my app is setup there is a top bar that is basically just a static image that has UIButtons placed on top of it. That is the Main View Controller and is persistent no matter what view is shown beneath it. I can't use a navigation controller because it is not possible to change the height and I need the bar to be significantly larger than a navbar. However my bar is functioning in much the same way. There is a "Home" Button, a "Back" Button and several destination buttons.
I understand how to switch views from say the home screen. My confusion comes with the back button. In order to press back the app is going to need to know what view is currently being displayed so that it can be removed from view and a new subview can be added. Ideally I would use the UINavigationController so that I can push and pop views which is really what I want to do here, however that is not possible because of the visual problem.
Does anybody know of a method that returns the current displayed view so I could do something like the following
[currentview.view removeFromSuperView];
[self.view insertSubview:experienceViewController.view atIndex:0]
You can use UINavigationController with the nav bar hidden. Put the nav controller inside a view that does have your jumbo toolbar and you'll have access to the push/pop behavior you're looking for.
I am trying to set up a Modal View Controller, that that lies below a fixed toolbar. therefore the toolbar is supposed to stay on top while the modal view rolls in.
the Safari-App does that for example, when hitting the bookmarks-button. the toolbar stays, the buttons change..
I tried a couple of things like pushing the toolbar to the front and ended up not using the presentModalViewController method at all, and animating the new View manually into a subview instead. but that brought a couple of other issues along.
I'm not sure what you are saying, when you press add bookmark in safari, a new modal view shows with no tool bar. The navigation bar at the top is not a tool bar if that is what you mean. They are UIToolbarItem set into self.navigationItem.
All modal views I've seen are animated until they take up the whole of the screen. Those modal-like views that only scroll up to a certain point in some apps, are done by hand. Maybe you can cover those issues encountered when doing this by hand in another post?