5

In Windows 8.1 when native SettingsFlyout is visible and I click elsewhere, either in my app or in other app, the flyout disappears.

Is there a way to keep it visible until I dismiss is manually? My use case - I want to display "login" SettingsFlyout that won't disappear when user leaves the app and searches for his login name and password.

I've checked MSDN pages for it, but found no simple property for "Sticky" flyout.

Thanks for any hint!

Martin Suchan
  • 10,600
  • 3
  • 36
  • 66

2 Answers2

6

There is one way to do it without using the Callisto library with the default controls within the SDK.

public class CustomSettingsFlyout : SettingsFlyout
{
    bool back = false;
    private Popup popup;
    public void ShowWindow()
    {
        ShowIndependent();
        back = false;
        popup = (Parent as Popup);
        popup.IsLightDismissEnabled = false;
        popup.Closed += Popup_Closed;
        this.BackClick += CustomSettingsFlyout_BackClick;
    }

    void CustomSettingsFlyout_BackClick(object sender, BackClickEventArgs e)
    {
        back = true;
    }

    private void Popup_Closed(object sender, object e)
    {
        if (!back) popup.IsOpen = true;
    }



}

Now call the ShowWindow method is place of ShowIndependent on the new control.

CustomSettingsFlyout flyout = new CustomSettingsFlyout();
flyout.Content = new Grid();
flyout.ShowWindow();
Shubhan
  • 874
  • 7
  • 13
  • This worked for me, except the flyout closes briefly then reopens the first time you click outside it. But it is also very helpful when debugging flyouts since they close when you enter a breakpoint. – Tommy Ovesen Feb 18 '14 at 19:20
  • @Shubhan - Can we achieve the same thing by using pure XAML without code-behind? – HelpMatters Aug 07 '14 at 16:38
  • @Shubhan - When the app is moved between 2 screens of different resolution, these settings flyout UI gets messed up. – HelpMatters Aug 27 '14 at 15:50
1

There's no way to use the default API to make the SettingsFlyout "sticky" like the AppBar. The best way to achieve your scenario would be to make a custom SettingsFlyout-like Popup; the Callisto library implements one, and you can turn off IsLightDismissEnabled on the Popup to make it "sticky".

Valen
  • 423
  • 3
  • 4
  • The Callisto control you are pointing to says OBSOLETE (and deprecated). It suggests us to use the SettingsFlyout provided by Microsoft. – HelpMatters Aug 23 '14 at 09:01
  • 1
    It's deprecated if you just want a SettingsFlyout. If you want to make a custom control that is similar to a SettingsFlyout then it is a good place to start. – James Newton-King Dec 02 '15 at 01:49