Log In
[Expand]General Information
[Collapse]WinForms Controls
 [Expand]What's Installed
 [Expand]Build an Application
 [Collapse]Controls and Libraries
  [Expand]Forms and User Controls
  [Expand]Messages, Notifications and Dialogs
  [Expand]Editors and Simple Controls
  [Expand]Ribbon, Bars and Menu
  [Collapse]Application UI Manager
    [Expand]Widget View
    [Collapse]WindowsUI View
     [Expand]Getting Started
      Windows UI Guidelines
      Content Containers
      Navigation Bars
      WindowsUI Buttons
      Search Panel
      Hierarchy and Screens
      Navigating Through Containers
     Tabbed View
     Native MDI View
     Document Selector
     Non-Document Mode
   [Expand]Deferred Load
   [Expand]Interaction with Dock Panels
   [Expand]Bar and Ribbon Merging
  [Expand]Docking Library
  [Expand]Data Grid
  [Expand]Vertical Grid
  [Expand]Pivot Grid
  [Expand]Tree List
  [Expand]Chart Control
  [Expand]Map Control
  [Expand]Rich Text Editor
  [Expand]Spell Checker
  [Expand]Form Layout Managers
  [Expand]Navigation Controls
  [Expand]PDF Viewer
  [Expand]TreeMap Control
 [Expand]Common Features
  Get More Help
 [Expand]API Reference
[Expand]ASP.NET Controls and MVC Extensions
[Expand]ASP.NET Bootstrap Controls
[Expand]WPF Controls
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Document Server
[Expand]Report Server
[Expand]eXpressApp Framework
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation

Hierarchy and Screens

Expanded Online Video

Expanded Hierarchy and Screens

WindowsUIView-based applications consist of multiple screens connected to each other. Each screen displays a specific Content Container or Document. Screens are linked to each other to form an application hierarchy that can be viewed and modified via the Designer's 'Navigation Tree' section.

In the figure above, the topmost container is the TileContainer with 3 Tiles added to its Items collection.

Clicking a tile within the TileContainer at runtime displays a screen whose content is specified by the tile's Activation Target. The Activation Target can be a Content Container or a Document. Child nodes of the application hierarchy are aware of their parents, making it possible to navigate back from the current screen to upper levels.

Typically, a Windows UI application has a TileContainer as the start-up container. By default, the first container at the top-most hierarchy level is displayed at start-up. You can handle the WindowsUIView.QueryStartupContentContainer event to manually set the start-up container.

How would you rate this topic?​​​​​​​