StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I have a similar setup which uses data templates and it works just fine with inherited classes. This is how I did it.</p> <pre><code><ListBox Name="UserList" ItemsSource="{Binding Path=Users}" ItemTemplate="{StaticResource ShowUserName}" SelectedItem="{Binding Path=SelectedUser, Mode=TwoWay}"> </ListBox> <ContentControl Content="{Binding ElementName=UserList, Path=SelectedItem}"/> </code></pre> <p>In the Window.Resources section I have the following DataTemplates:</p> <pre><code><DataTemplate x:Key="ShowTime" DataType="TestApp.User"> <TextBlock Text="{Binding Path=Name}" HorizontalAlignment="Center"/> </DataTemplate> <DataTemplate DataType="{x:Type local:User}"> <StackPanel Margin="10"> <TextBlock Text="{Binding Path=Name}"/> <TextBlock Text="{Binding Path=Age}"/> </StackPanel> </DataTemplate> <DataTemplate DataType="{x:Type local:Author}"> <StackPanel Margin="10"> <TextBlock Text="{Binding Path=Name}"/> <TextBlock Text="{Binding Path=Age}"/> <TextBlock Text="{Binding Path=FirstTitle}"/> </StackPanel> </DataTemplate> </code></pre> <p>The first template is what will be displayed in the list itself. We are referencing it by key in the ItemTemplate property of the listbox. The other two data templates are used by the content control when determining what to display for the selected item. When the selected item is just a User, the User DataTemplate will be displayed, if an author is selected, the author DataTemplate will be shown.</p> <p>The x:Type local:Author is referring to the the class type. local should be declared in your namespace declarations.</p> <pre><code>xmlns:local="clr-namespace:TestApp" </code></pre> <p>Keep in mind that this is my namespace, you will have to specify the one you are using. And of course the data templates are just basic examples, presumably you will want to do something more tailored to your application.</p> <p>However it might be irritating to have to define two separate Data templates that are almost exactly the same for your two classes. Although you certainly could. I do it in my own application (not in this example), because what I want to display for each type are vastly different.</p> <p>So what might be useful is to create a common DataTemplate for all the User properties, and simply extend this DataTemplate for Authors. If you want to do that you could set up your templates this way:</p> <pre><code><DataTemplate x:Key="UserTemplate">  </DataTemplate> <DataTemplate DataType="{x:Type local:User}"> <ContentPresenter Content="{Binding}" ContentTemplate="{StaticResource UserTemplate}"/> </DataTemplate> <DataTemplate DataType="{x:Type local:Author}"> <StackPanel> <ContentPresenter Content="{Binding}" ContentTemplate="{StaticResource UserTemplate}"/>  </StackPanel> </DataTemplate> </code></pre> <p>So as you can see, both of the DataTemplates for User and for Author start out using the DataTemplate called "UserTemplate". But in the Author DataTemplate we will add Author specific properties.</p> <p>I hope that helps.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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