I opened a user voice feature request for the ability to put the master fly out in the master detail page on the right instead of the left. I was also wondering if someone here might have already worked out a work around? Has anyone had any success?
I was actually able to pull this off fairly easily (only done for iOS at this point) by implementing the NavigationPage and adding a bindable property to store the color I wanted and then having a custom renderer take that property and set it. I did the same for the title text color because I didn't see a way to do it. In total it would only about 20 lines of code (most of them boilerplate) and it works like a dream on iOS. I will be implementing it for Android and WP (so long as they support it) in the next week or so. I can see about posting it when I get back to my code later. It is worth it to note this is only color.. I don't think you can use an image or anything like that.
Is there plans to provide the ability to disable the button that is added to the navigation bar when the navigation page is a part of the MasterDetailPage? I looked at doing it by overriding the renderer for Navigation page but couldn't get it to work just right. I think I could make it happen if UpdateLeftBarButtonItem was protected virtual so I could override and make it act the way I want it to if there is no plans to give us the ability to disable the button built in.
Not a certain custom renderer but I would like to see the creation of the native control moved out of a function filled with other code... at least on specific renderers like the button one. The reason I would like to see this is on iOS (I had to overcome it for iOS but might have similar issues on WP and Android) you guys are doing the following:
The rest of the functionality would have worked fine but since I had to not let the ButtonRenderers OnModelSet get called I had to reimplement the entire renderer which was not desired. Now, I know doing something like I am suggesting could cause issues if someone decides to return a MKMapView when you are expecting a Button so you could implement it with generics at your NativeRenderer level so you can enforce that you get a UIButton back (in this example at least) by setting the return type of the function. Something like this could also be useful in other situations for example I ported MapBox's MBXMapKit over to Xamarin's C# goodness. If you open up Xamarin.Forms.Maps renderers to customization (they are currently internal I believe) I could use the above suggestion to pass in my new MapView type because MBXMapKit inherits MKMapView. This would allow me to not do a lot of the boiler plate code you guys already wrote.
No more internal! I know there is a good reason for internal accessibility but it has tripped me up and make me have to reimplement perfectly working code because I can't make one function call on a class I am inheriting from. So I would like to see more use of Protected if you don't want the outside world to be able to get at it.
First of all i would like to say I am loving the new updates!
Ok, so I am working on an application that I do some processing during load of the application so I start on a Splash Screen. Once the processing is complete I take the user to one of two other Pages depending on the results of my processing. This works wonderfully.... except that I push the Splash Screen onto a NavigationPage in my GetMainPage function call as I want to use the Navigation page for the rest of the application. What this allows the user to do is hit their back button from the page I push them on to and it takes them back to the Splash Screen! I am in search of a way to make the navigation page essentially ignore the Splash Screen page. I thought of two ways this is possible but am not sure if either are possible...
Any help on keeping a page out of the navigation history would be greatly appreciated!