This is my first iPhone project and all has been going very well but I've run into a small snag that I can't seem to find a good solution for. Thanks in advance to everyone who takes their time to help me out.
I have a very straight forward Tab Bar application with a few tabs. Each tab defines a subsection that is controlled with a Navigation Bar. The client now wants to place a button in one of the views of the subsection that "deep links" into a view of a different section ( different tab).
To Illustrate:
Root
- Tab 1 (Bedrock)
- Navigation Controller
- Fred View
- Wilma View
- Betty View
- Barney View
- Tab 2 (Mystery Machine)
- NC
- Scooby View
- Shaggy View
- Daphnie View
...
The client would like a button in 'Barney View' that opens up 'Shaggy View'
What is the best way to accomplish this?
You will want to use the selectedViewController or selectedIndex property of the UITabBarController to switch tabs, and the viewControllers property of the UINavigationController to set the view stack.
Related
I have created single category back end view. I mapped back end view to view panel control in xpages in notes 9 and set the following property to open xpage view in collapse mode.
expandLevel is "1" in All Properties of xpage view panel.
Initially view panel is displaying in collapsed mode. when i expand any category, its expand the category and show the list of document(Default 30 entries will display). I like to navigate to next page to see rest of document and categories. But when i expand the category, pager page count is not changed. its not calculating the pages. I unable to find link enable to navigate in pager.
Its work for me in notes 853 and notes 852.
any one else facing issue? To reproduce issue just create single category backend view(make sure have more document to display in more pages) and map to xpage view control and disable expand level property
Its not work for me in both web browser and xpinc.
is problem with notes 9? or something else? Do i need to enable any other setting in notes 9 to make work?
Using categories in views is not a recommended UI pattern for web applications, so you might actually consider using an alternative.
I am building a site using the Zurb Foundation UI framework, and I am wondering how to go about top-level navigation links so that they work for both desktop and mobile visitors.
EDIT: Here's an example: http://meowzen.com/zurb-nav/
Section 1 <-- should take the visitor to a "section" page
--Sub-Section 1 <-- should take the visitor to a "sub-section" page
--Sub-Section 2 <-- ditto
--etc
In the example via the link above, you'll notice that all links work as expected on a large screen. However, when the responsive navigation kicks in (either by resizing the window or viewing the page on a mobile device), the "section" pages aren't accessible through the menu anymore.
Has anyone come up against this problem? Do you have any suggestions on how to go about this?
Many thanks in advance!
EDIT: Here are some options I have at the moment:
Option 1: Only show top-level 'sections' for the mobile navigation - here's an example: projection . pixar . com . <- I'm leaning towards this!
Option 2: Make the section names linkable - I believe it's possible because there's a working example here: emerilsrestaurants . com .
Option 3: Insert a dummy menu item for the section pages at the sub-section level .
In the example via the link above, you'll notice that all links work as expected on a large screen. However, when the responsive navigation kicks in (either by resizing the window or viewing the page on a mobile device), the "section" pages aren't accessible through the menu anymore.
I am not sure I am understanding you correctly, but your example is working as expected. For smaller viewports ("mobile" view) the menu is hidden in a dropdown component. Once you drop down the menu, sub-menu items are still navegable on click.
Currently in my app I have this design:
-- DialogViewController 1
-----DialogViewController 2
--------DialogViewController 3
-----------TabBarController
--------------DialogViewController4
--------------DialogViewController5
--------------DialogViewController6
--------------DialogViewController7
Problem with this is that dialog view controllers 4-7 breaks the monotouch dialog flow (so to speak), because of TabBarController in between. When I create dialog view controllers 4-7 I need to create new Root in their constructors which I don't need to for DVC 1-3.
With this approach certain things like radio groups don't work inside DVC 4-7 e.g it will display the radio group selection, but there is no navigation bar at the top.
My question is what can I do to solve this? Can I use TabBarController inside DVC somehow if that makes sense? Or how can I "hook" DVC 4-7 back to main "circuit"?
Thanks in advance.
According to the iOS HIG
A tab bar appears at the bottom edge of the screen and should be
accessible from every location in the app
which implies that it should be the root, not nested inside another controller.
This is what I want to do but not sure if it could be done.
my first view contains 3 buttons.
When this view is displayed, I need to present a ModalPopup for the login.
When the authenfication is done, the user can tap on one of the 3 buttons.
When the button is taped, I need to switch this view to a TabBarController and active the correct TabBarItem regarding the button.
Most of the TabBarItems can contain a SplitViewController.
I read several posts and tutorial about the SplitViewController but most of them show how to run a splitViewController from the appDelegate controller.
Then my first question would be.. is it possible :-)
The second one, would be, how?
Thanks...
Mortoc is correct about UISplitViewController needing to be the root controller.
You can use MGSplitViewController as a drop-in replacement for UISplitViewController - and it doesn't have this limitation.
It sounds as if your hierarchy might be something like
UINavigationController (root)
UIViewController (3 buttons)
UITabBarController
MGSplitViewController (1)
MGSplitViewController (n)
Sorry, you'll have to roll your own SplitViewController equivalent. Apple only supports UISplitViewController as the root view item: it has to be the first view loaded in your application and it's size is fixed.
http://developer.apple.com/library/ios/#featuredarticles/ViewControllerPGforiPhoneOS/iPadControllers/iPadControllers.html
If I am on page
http://mysite.com/first/second/third/Wiki/pages/home.aspx
and click the Navigate Up button I can see the following hierarchy (whis is correct):
Home - first - second - third - Wiki
But if I navigate up one step to
http://mysite.com/first/second/third/SitePages/Home.aspx
and click the Navigate Up button again the first subsite is not showing up.
Home - second - third - Home
I set the navigation settings to be identical on both sites but still the same issue/error.
How can I fix this?
Cheers
A few things you can try....
In your masterpage / page layout, find your SiteMapPath control. This has a property called ParentLevelsDisplayed. If you set it to -1 (the default) it should show all parent sites in the breadcrumb. Also, make sure that the SiteMapProvider is the same for both controls on both pages.
In your /second subsite, check whether or not the global navigation is set to inherit from its parent. This setting will affect how the breadcrumb is displayed, more on this [here].
Third (and this only applies to publishing sites), open the page layout that your Home.aspx page is referencing. Search for PlaceHolderTitleBreadcrumb. Lots of the OOTB layouts override this placeholder and construct their own breadcrumb. There is a great list [here] of all the layouts and their individual breadcrumb settings.
Hopefully this helps!