I've encountered an issue with the navigation bar height in the iOS version of my Xamarin Forms Prism app whereby it appears to be double height.
It displays correctly on Android.
I navigate to the page in the normal Prism way (ViewDaily is a Detail of the MasterDetailPage MainPage):
await NavigationService.NavigateAsync("/MainPage/NavigationPage/ViewDaily");
But the same also happens if I navigate to as a normal Navigation Page. This isn't my use case as I need the MasterDetail Page but i tried as a test:
await NavigationService.NavigateAsync("/NavigationPage/ViewDaily");
Any help gratefully received.
Navigate to ViewDaily only, otherwise you add another navigation page...
await NavigationService.NavigateAsync("ViewDaily");
Thanks to Dan Siegel for the answer:
https://github.com/PrismLibrary/Prism/issues/2511
Add the following to the Detail (Content) Page:
ios:Page.LargeTitleDisplay="Never"
Related
I am using master detail page. In iOS when I click hamburger icon the master page slides the detail page to right in iOS. I want when we click on hamburger icon the master page should come over detail page like in android. The detail page should not slide to right, it should stable and Master page should overlap it in ios. In android its working fine. How can I achieve it in ios also?
In your Master Detail Page Xaml or CS file you need to set the attribute MasterBehaviour to be equal to the type Popover.
You must then on pressing the hamburger icon change the IsPresented variable from false to true or the reverse if you would like to slide the drawer out or back in.
Xamarin.Forms currently (v3.40) have a pretty terrible implementation of the MasterDetailPage I have raised issues on GitHub and I am currently working on a pull request to fix their bugs for them.
I am using Prism for Xamarin Forms application development.
May be because I am new to both Prism and Xamarin Froms because of which I am facing a basic issue with the navigation.
Let me start with the details of my implementation and then the issue at hand.
I have a MasterDetail Page (named Home) which is my main page.
There are a few menu items in the Master Page. One of them is Partner.
On Click of Partner menu item, NavigationService.NavigateAsync("Navigation/Partner") method is called. Where "NavigationService" is of type "INavigationService".
This opens a page called "Partner" which is a tabbed page (TabbedPage). The first tab is a contentpage called "PartnerAll".
PartnerAll page contains a listview. On click of a list view item, a new page is opened "PartnerDetails" by calling NavigationService.NavigateAsync("Navigation/PartnerDetails", parameters, false, true);
On PartnerDetails page, I have added a toolbaritem called "Cancel".
Issue: When "PartnerDetails" page opens up, "Cancel" item shows up twice, as shown in the screenshot:
screenshot of partner details page with two cancel buttons
Where is it I am going wrong. What should I do to make it work?
Please assist.
Best regards, Ankur Jain
You’re pushing two NavigationPage’s onto the Navigation Stack. This would result in two Navigation bars. You can see in your screenshot you have both a back and a hamburger menu icon.
You should just pass in the identifier string for your destination page, instead of pushing another instance of the NavigationPage onto the stack
do it like so NavigationService.NavigateAsync(PartnerDetails);
I am using Xamarin Forms with Prism. How do you navigate from the MasterDetail.Master to a ContentPage that is not part of the MasterDetail (that is, I don't want to just update the detail and continue to be part of the Master/Detail relationship)? The use case is like the Gmail app when you click on Settings from the Hamburger menu. It takes you out of the Master/Detail and you are now in a NavigationPage/ContentPage with a back button to get back to the MasterDetail page.
If you were not using Prism you could go to the Detail page and do a Navigation.PushAsync from there:
var mdp = Application.Current.MainPage as MasterDetailPage;
mdp.IsPresented = false;
await mdp.Detail.Navigation.PushAsync(new ContentPage2());
But I don't see how to do this using Prism navigation.
-Steve
Assuming your Application.Current.MainPage is a MasterDetailPage. Current Detail in the MasterDetailPage is NavigationPage(new ContentPage1()).
In your ContentPage1, you have 2 options to navigate to ContentPage2:
Option 1: Show ContentPage2 in current navigation stack
You will be pushing ContentPage2 into the same Navigation stack of ContentPage1. Back button in navigation bar will be added automatically.
// Call this code in ContentPage1
_navigationService.PushAsync("ContentPage2");
Option 2: Show ContentPage2 modally
You are presenting the page modally and in a completely new navigation stack. You will need to add Back button in the NavigationBar and handle the click event with your own code.
// Call this code in ContentPage1
_navigationService.PushAsync("NavigationPage/ContentPage2", null, true);
I'm using Xamarin Forms with Prism and I need to create a layout with a sidebar menu and a fixed bar at the bottom of the screen with quick actions like instagram app for iOS and Android.
I was thinking in use MasterDetail but how can I add that fixed bar at bottom of the Detail controller and keep it when detail page changes?
And the second thing is that I have a specific page that has form sections separated by tabs, so how can I render tabs at the top of the page for iOS (like Android)?
Something like this:
I have several navigation pages that go several levels deep. Each time the user navigates to another page, an additional Back button is added to the top.
Navigation.PushAsync(new NavigationPage(new SettingsPage()));
Do I have to manually turn off the navigation bar prior to Pushing the new page or is there some type of setting for this?
Thanks.
Like Sushi mentioned in the comment, you're already in navigation page, you do not have to push a new NavigationPage every time.
Just use:
Navigation.PushAsync(new SettingsPage());
You can read more about navigation in Xamarin.Forms here: https://developer.xamarin.com/guides/xamarin-forms/user-interface/navigation/hierarchical/