So I have 3 main scenes, each with a tab bar item. The first scene (Account scene) contains a UITableView. Also on this scene I have a button which switches to a different scene that is NOT included on the tab bar.
ie. Account scene (which IS on tab bar) has button to link to Account Info page (which IS NOT on tab bar). This all works fine, but when I go back to the Account scene from the Account Info scene, the UITableView now is covering the Tab Bar (or the Tab Bar may have just disappeared altogether), so I can no longer access it and switch to different scenes.
Anyone else encountered something similar or know why this may be happening? If sample code is needed I can post some, but I did this mostly using storyboard.
Cheers,
Robin
Fixed. Was segue-ing to the view controller itself, instead of segue-ing to the TabBarController that handled the view. Limitation is that I can only segue back to the first tab bar view, which is kind of annoying but oh well.
Related
I have a navigation controller with a table full of buttons that cause various settings pages to push in. I needed to add a new one, so I copied one of my existing ones, changed the VC, and off I go.
But there's no nav bar on the screen. I can see the navigation object in the storyboard and the editor simulates it's display. I compared it to the other pages that are displaying the bar, and they look the same.
I tried changing some settings, like "Hide Bottom Bar On Push" and that had an effect, but my attempts to get the bar to show up fail.
I looked at other questions that suggested it had something to do with naming, but I've tried various name fields - on the Navigation Item, the VC's Title, etc. - with no effect.
I am not sure, but the problem may be that in case the segue to the new View Controller Scene is set to modal, it would not have a Nav Bar, To be able to see one, you need to embed that in another Navigation Controller.
I have the following storyboard setup:
I would expect, that the two UITabBarControllers (blue and red) connecter to the orange UINavigationController and each display the different view controller and the "shared" one. However when running the app only one of the UITabBarControllers (the red one) has both view controllers. The other UITabBarController (blue) only has one item in the tab bar, which is not the orange one.
I have given all the different view controllers unique ID's but it doesn't change anything.
I could just duplicate the orange view controller but that would sort of be inconvenient, as everything is the same and it would clutter the storyboard.
Is there a way to accomplish the desired result with out cloning the orange view controller (ie. through code somehow)?
I will list the steps as we just started a new project:
Here, we have only the starting view controller.
select it, click Editor on menu bar Embed in navigator controller.
add a view controller from the right-bottom window.
embed in with the new view controller, two tab bars.
connect the starting view controller with both of the tab bars with a push segues(using buttons).
customise both of the tab bars.
test by clicking the two buttons.
I hope this is clear and helpful.
This happened in the design time the later connected tab bar replaces some property of the previously connected tab bar. I don't think this can be fixed (at least the way we are doing it). if that property could be set to both tab bars the interface builder would do it for us. I don't think that could be solved.
I have an iOS App. I currently have an existing View Controller. I manually added a UI Tab Bar to it using the storyboard.
I added the UITabBarDelegate and implemented the corresponding functions required tabBar:tabBar didSelectItem:item.
I've also connected the delegate of the Tab Bar to the view controller itself.
However, when I build, the Tab Bar completely does not show up at all.
I know you can just use a Tab Bar Controller, but I need to add the Tab Bar to it, and use the Tab Bar to modify content of the view itself. (specifically it acts as a filter for a table view) So, it doesnt make sense to create 4 exact same Views to hook up to a UI Tab View Controller
What am I doing wrong?
I found out what's wrong.
It turns out, I had completely successfully implemented the UITabBar. What happened was that I was testing on an IPhone 4. As such, it bled out of the screen and could not be seen. Adding constraints fixed it.
I've got an iOS7 iPad app. I use storyboards. My root view controller is a tab bar controller. One of my tabs is a split view controller to view reports, which has a table view controller (embedded in a navigationController) in the left-hand split and view controller in the detail side.
I'm finding that I have a random bar across the bottom of both controllers. In the screen shot you can see it at the bottom of the left-hand pane. If I were to select a report which loads the detail side, you'd see the same thing there as well. No matter what I do I can't get it to go away... gotta be missing something simple. Any tips?
Here's the storyboard view. Note that there's some sort of a bar showing up in the Split view controller, but it's not there in the nav controller. I don't know if this bar is related to the problem or not. I suspect it's being inferred from the tabbarcontroller's bottom bar.
Bit of a strange one.
I have a UIButton which works when located anywhere on the view except the top left hand corner when in landscape mode.
I have a navigation bar with a back button nested in the same area but when the the video enters full screen and playback state changes this navigation bar is hidden.
any ideas?
As thought, the problem was occuring due to the hidden navigation bar and the navigation item located in the same place.
The only solution i can find was to remove the navigation bar from superview then add it back when needed.
Your view's hierarchy is not properly configured. To properly configure your hierarchy, you need to navigate to either the xib or storyboard that you're working with, and re-order the button so that it's on top of anything that falls within it's similar bounds. A common example is that you added a UIView, which is clear, and you had the button underneath it, and now you can't interact with it even though you can't see it.