Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to open any specific SettingsFlyout in WinRT app
    primarykey
    data
    text
    <p>I am working on a Windows 8 metro app and having multiple SettingsFlyout items which get added by below mentioned code </p> <pre><code>SettingsCommand cmd1 = new SettingsCommand("sample", "Color Settings", (x) =&gt; { // create a new instance of the flyout SettingsFlyout settings = new SettingsFlyout(); // set the desired width. If you leave this out, you will get Narrow (346px) // optionally change header and content background colors away from defaults (recommended) // if using Callisto's AppManifestHelper you can grab the element from some member var you held it in // settings.HeaderBrush = new SolidColorBrush(App.VisualElements.BackgroundColor); settings.HeaderBrush = new SolidColorBrush(Colors.Black); settings.HeaderText = string.Format("Color Settings", App.VisualElements.DisplayName); settings.Background = new SolidColorBrush(_background); settings.Margin = new Thickness(0); // provide some logo (preferrably the smallogo the app uses) BitmapImage bmp = new BitmapImage(App.VisualElements.SmallLogoUri); settings.SmallLogoImageSource = bmp; // set the content for the flyout settings.Content = new ColorSettings(); settings.HorizontalAlignment = Windows.UI.Xaml.HorizontalAlignment.Stretch; // open it settings.IsOpen = true; // this is only for the test app and not needed // you would not use this code in your real app // ObjectTracker.Track(settings); }); </code></pre> <p>Currently using (SettingsPane.Show()) i can be able to show the added flyout items list but I want to programmatically open any setting Flyout item instead of opening a flyout list.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload