Background, Working, and Notification Views
Written By launchbox
Last updated About 1 month ago
Not every LaunchBox themed view is a main layout surface. Some views support the overall experience by drawing background artwork, progress overlays, and notifications.
The main supporting views are ContentBackgroundView.xaml, WorkingView.xaml, NotificationView.xaml, and NotificationListView.xaml. These files are smaller than the main content views, but they still have important bindings that should be preserved.
ContentBackgroundView
ContentBackgroundView.xaml displays the current background image behind the rest of the LaunchBox interface. It is hosted from MainView.xaml through the ContentBackgroundViewModel transition presenter.
<transitions:TransitionPresenter x:Name="ContentBackgroundViewModel" Content="{Binding ContentBackgroundView}" />The default view contains an Image named Image. LaunchBox finds this image by name and assigns the loaded background source directly when the view attaches.
<Image Name="Image" HorizontalAlignment="{Binding HorizontalAlignment}" VerticalAlignment="{Binding VerticalAlignment}" Stretch="{Binding Stretch}" />If you customize this view, keep an image named Image unless you are intentionally replacing the background behavior. LaunchBox also supports an optional image named ClearLogoImage for layouts that use clear logo artwork with the background.
Background Bindings
ContentBackgroundViewModel exposes these layout bindings:
The default view hides the placeholder background image path so the built-in fallback does not show as a real themed background.
WorkingView
WorkingView.xaml displays LaunchBox's progress overlay for long-running tasks. It is hosted by MainView.xaml through a ContentControl named WorkingViewModel.
<ContentControl x:Name="WorkingViewModel" Visibility="{Binding WorkingVisibility}" />This view is behavior-sensitive because users may need to see progress, cancel a task, or open an errors link.
WorkingView Bindings
Important WorkingView.xaml bindings include:
The cancel button should remain named Cancel, and the error hyperlink should remain named ErrorLink. LaunchBox uses those elements for built-in cancel and error behavior.
NotificationView
NotificationView.xaml controls the appearance of a single notification. It is used both for tray-style notifications and for notifications inside the notification list.
Important bindings include:
The default view also includes a dismiss button named Dismiss. Keep that action available if you want users to be able to close notifications from the themed notification item.
NotificationListView
NotificationListView.xaml controls the notification panel. It displays the current notifications collection and a clear-all action.
ItemsSource="{Binding Notifications}" Command="{Binding DismissAllCommand}"Important bindings include:
When rebuilding the list, keep the Notifications items source and the empty-state visibility logic so the panel works correctly when there are no notifications.
What You Can Safely Customize
Background image presentation and overlays
Progress bar styling and animation
Working overlay shape, position, spacing, and colors
Notification card backgrounds, borders, spacing, and typography
Read/unread visual states
Notification tray styling versus list styling
Clear-all and dismiss button appearance
What to Be Careful With
Keep the background image named
ImageinContentBackgroundView.xaml.Keep the optional
ClearLogoImagename if you use clear logo background behavior.Preserve
Maximum,Value, andIndeterminateinWorkingView.xaml.Keep the
Cancelbutton available if users should be able to cancel tasks.Keep the
ErrorLinkhyperlink if you show task errors.Preserve notification
Message,Icon,Buttons, and dismiss behavior.Keep
Notificationsbound inNotificationListView.xaml.
Related Articles
In Short
The supporting LaunchBox theme views handle background artwork, progress overlays, and notifications. They are good places for visual polish, but several named controls and bindings are used directly by LaunchBox. Preserve those pieces so background loading, progress reporting, cancellation, errors, and notification actions continue to work.