Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>CurrentView should be a property om your MainWindowViewModel or whatever class that is your Datacontext on Window.xaml. For each view you define a data template. The data template can contain the view or point to a user control. Assign the CurrentView to a view model to switch view. Here is some code:</p> <p><strong>MainWindowViewModel</strong></p> <pre><code>public class MainWindowViewModel : ViewModel { object currentView; public MainWindowViewModel() { CurrentView = new OptionalView(); SwitchViewCommand = new RelayCommand(SwitchView); } public object CurrentView { get { return this.currentView; } set { this.currentView = value; NotifyPropertyChanged("CurrentView"); } } public RelayCommand SwitchViewCommand { get; set; } void SwitchView() { if (CurrentView is OptionalView) CurrentView = new SettingsView(); else CurrentView = new OptionalView(); } } public class OptionalView { } public partial class SettingsView { } </code></pre> <p><strong>MainWindow</strong></p> <pre><code>&lt;Window x:Class="WpfLab.Views.MainWindow" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:views="clr-namespace:WpfLab.Views" xmlns:vm="clr-namespace:WpfLab.ViewModels" Title="MainWindow" Width="525" Height="350"&gt; &lt;Window.Resources&gt; &lt;DataTemplate DataType="{x:Type vm:OptionalView}"&gt; &lt;Border Background="Red" /&gt; &lt;/DataTemplate&gt; &lt;DataTemplate DataType="{x:Type vm:SettingsView}"&gt; &lt;views:SettingsView /&gt; &lt;/DataTemplate&gt; &lt;/Window.Resources&gt; &lt;Grid&gt; &lt;Grid.RowDefinitions&gt; &lt;RowDefinition Height="*" /&gt; &lt;RowDefinition Height="Auto" /&gt; &lt;/Grid.RowDefinitions&gt; &lt;ContentControl Content="{Binding CurrentView}" /&gt; &lt;Button Grid.Row="1" Command="{Binding SwitchViewCommand}" Content="SwitchView" /&gt; &lt;/Grid&gt; </code></pre> <p></p> <p> <strong>Settings View</strong></p> <pre><code>&lt;UserControl x:Class="WpfLab.Views.SettingsView" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:d="http://schemas.microsoft.com/expression/blend/2008" xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006" d:DesignHeight="300" d:DesignWidth="300" mc:Ignorable="d"&gt; &lt;Border Background="Green" /&gt; </code></pre> <p></p>
    singulars
    1. This table or related slice is empty.
    1. POHow to fill a MainWindow with one of two UserControls using a local variable
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPatrick
    1. USPer
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to fill a MainWindow with one of two UserControls using a local variable
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. COPer - Understand what you are suggesting - having CurrentView as a public property is obviously necessary - but how do you bind either usercontrol through that property (meaning if the property in the MainWindowViewModel is set as value = OptionalView) - then how do you translate that in the Mainwindow.xaml and render the Optional View user control. Assumption here is that the usercontrols do not have any ViewModels and are simple usercontrols (having just plain XAML code)
      singulars
      1. PO
      1. USPatrick
    2. COI have updated my answer. Even if you don't need a separate view model fore each view it's an easy way for rendering different views.
      singulars
      1. PO
      1. USPer
    3. COThanks Per, I had vacillated between separate view model(s) for each view and not, so I have no preference at the moment, nor specific need for it from an app requirement standpoint. I'll see what this does for me now.
      singulars
      1. PO
      1. USSleff
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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