Here is how to get this accomplished with Callisto: SettingsFlyout settings = new SettingsFlyout() In addition to the narrow SettingsFlyout (346px in width) there is also a wide alternative (646px) which may help if there's a lot of text to display. If this is not applicable, there's also no problem in displaying a ScrollViewer within the flyout. Regarding the amount of settings you should only display those a user will really need (KISS principle). You should think about grouping the settings in different flyouts and entry points. What if I have a lot of "settings" and want a full page for them? They say to always have settings in the charm bar and always use a flyout from the charmbar. You should consider this in order to pass the Windows Store certification successfully. Guidelines for app settings state that no navigation should be performed when activating an entry point and navigation commands should be placed in the app bar. SettingsFlyout which will be a huge help here - and they are accessible from everywhere in the code.Įxample: var SettingsFlyout = new SettingsFlyoutĬontent = new ImprintFlyout(), //use own user control here TheĬallisto toolkit includes a nice control called However, you should definitly use a flyout in order to present the application's settings. For example, it can be successully done in the code-behind of a Page or LayoutAwarePage since you can access the Frame property there, whereas it may not work in This approach works only if the app's frame is present and accessible in the current context.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |