Skip to main content

UWP - How to use SplitView

UWP SplitView
The SplitView class represents a container with two views. One view is for the main content and another view is typically used for navigation commands. The following UWP app development tutorial will demonstrate how we can use SplitView control in our app.

The UWP app developers use a SplitView control to present two areas, one is a Pane and another one is the main Content. The developers commonly put a SplitView to create a top-level navigation user experience that adapts to different screen widths following the nav pane pattern or the master and details pattern.

The SplitView’s Content area is always present and it can contain a single child element, which is normally a Panel that contains additional child elements. The Content can be completely covered by the Pane.

The SplitView class’s IsPaneOpen property gets or sets a value that specifies whether the SplitView pane is expanded to its full width. This property value is a Boolean.

The SplitView class’s CompactPaneLength property gets or sets the width of the SplitView pane in its compact display mode. The default value is 48 DIP.

The SplitView class’s OpenPaneLength property gets or sets the width of the SplitView pane when it's fully expanded. The default value of this property is 320 DIP.The SplitView class’s DisplayMode property gets or sets a value that specifies how the pane and content areas of a SplitView are shown. This property value is a SplitViewDisplayMode enumeration value. The default value of this property is Overlay.

The SplitView class’s PanePlacement property gets or sets a value that specifies whether the pane is shown on the right or left side of the SplitView.
MainPage.xaml

<Page
    x:Class="UniversalAppTutorials.MainPage"
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    xmlns:local="using:UniversalAppTutorials"
    xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
    xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
    mc:Ignorable="d"
    >
    <SplitView
        x:Name="SplitView1"
        DisplayMode="CompactOverlay"
        Background="CornflowerBlue"
        IsPaneOpen="False"
        CompactPaneLength="75"
        OpenPaneLength="200"
        Margin="50"
        >
        <SplitView.Pane>
            <StackPanel 
                Orientation="Vertical" 
                Background="LightSkyBlue" 
                Padding="20"
                >
                <Button 
                    x:Name="HamburgerButton" 
                    FontFamily="Segoe MDL2 Assets" 
                    Content=""
                    Background="Transparent" 
                    Click="HamburgerButton_Click"
                    Margin="5"
                    Padding="5"
                    />
                <Button x:Name="ButtonSave" Margin="5">
                    <StackPanel Orientation="Horizontal">
                        <SymbolIcon Symbol="Save"/>
                        <TextBlock Text="Save" Margin="10,0,0,0"/>
                    </StackPanel>
                </Button>
                <Button x:Name="ButtonPaste" Margin="5">
                    <StackPanel Orientation="Horizontal">
                        <SymbolIcon Symbol="Paste"/>
                        <TextBlock Text="Paste" Margin="10,0,0,0"/>
                    </StackPanel>
                </Button>
                <Button x:Name="ButtonCopy" Margin="5">
                    <StackPanel Orientation="Horizontal">
                        <SymbolIcon Symbol="Copy"/>
                        <TextBlock Text="Copy" Margin="10,0,0,0"/>
                    </StackPanel>
                </Button>
                <Button x:Name="ButtonCut" Margin="5">
                    <StackPanel Orientation="Horizontal">
                        <SymbolIcon Symbol="Cut"/>
                        <TextBlock Text="Cut" Margin="10,0,0,0"/>
                    </StackPanel>
                </Button>
            </StackPanel>
        </SplitView.Pane>
        <SplitView.Content>
            <StackPanel 
                Background="PaleGreen" 
                Padding="20" 
                VerticalAlignment="Center"
                Margin="50"
                >
                <TextBlock
                    Text="Content of SplitView"
                    FontSize="20"
                    TextWrapping="Wrap"
                    />
            </StackPanel>
        </SplitView.Content>
    </SplitView>
</Page>
MainPage.xaml.cs

using Windows.UI.Xaml.Controls;
using Windows.UI.Xaml;


namespace UniversalAppTutorials
{
    public sealed partial class MainPage : Page
    {
        public MainPage()
        {
            this.InitializeComponent();
        }

        private void HamburgerButton_Click(object sender, RoutedEventArgs e) {
            // Alter the pane close open state
            SplitView1.IsPaneOpen = !SplitView1.IsPaneOpen;
        }
    }
}
Labels:

Popular posts from this blog

Restricting Jetpack Compose TextField to Numeric Input Only

Jetpack Compose has revolutionized Android development with its declarative approach, enabling developers to build modern, responsive UIs more efficiently. Among the many components provided by Compose, TextField is a critical building block for user input. However, ensuring that a TextField accepts only numeric input can pose challenges, especially when considering edge cases like empty fields, invalid characters, or localization nuances. In this blog post, we'll explore how to restrict a Jetpack Compose TextField to numeric input only, discussing both basic and advanced implementations. Why Restricting Input Matters Restricting user input to numeric values is a common requirement in apps dealing with forms, payment entries, age verifications, or any data where only numbers are valid. Properly validating input at the UI level enhances user experience, reduces backend validation overhead, and minimizes errors during data processing. Compose provides the flexibility to implement ...
Read more

jetpack compose - TextField remove underline

Compose TextField Remove Underline The TextField is the text input widget of android jetpack compose library. TextField is an equivalent widget of the android view system’s EditText widget. TextField is used to enter and modify text. The following jetpack compose tutorial will demonstrate to us how we can remove (actually hide) the underline from a TextField widget in an android application. We have to apply a simple trick to remove (hide) the underline from the TextField. The TextField constructor’s ‘colors’ argument allows us to set or change colors for TextField’s various components such as text color, cursor color, label color, error color, background color, focused and unfocused indicator color, etc. Jetpack developers can pass a TextFieldDefaults.textFieldColors() function with arguments value for the TextField ‘colors’ argument. There are many arguments for this ‘TextFieldDefaults.textFieldColors()’function such as textColor, disabledTextColor, backgroundColor, cursorC...
Read more

jetpack compose - Image clickable

Compose Image Clickable The Image widget allows android developers to display an image object to the app user interface using the jetpack compose library. Android app developers can show image objects to the Image widget from various sources such as painter resources, vector resources, bitmap, etc. Image is a very essential component of the jetpack compose library. Android app developers can change many properties of an Image widget by its modifiers such as size, shape, etc. We also can specify the Image object scaling algorithm, content description, etc. But how can we set a click event to an Image widget in a jetpack compose application? There is no built-in property/parameter/argument to set up an onClick event directly to the Image widget. This android application development tutorial will demonstrate to us how we can add a click event to the Image widget and make it clickable. Click event of a widget allow app users to execute a task such as showing a toast message by cli...
Read more