StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>You're really going to create the inheritance in your view models, not your views. I'd define an <code>ItemViewModelBase</code> class that exposes <code>ItemName</code>, <code>Items</code>, and <code>SelectedItemName</code> properties and derive my view models from it. </p> <p>The views themselves don't really "inherit" per se. In fact, unless you need customization in the view, you don't need multiple views: you only need one view that presents <code>ItemViewModelBase</code> objects. </p> <p>Of course, if you do need the views to be different, you can do a certain amount of customization, e.g.:</p> <pre><code><DataTemplate DataType="{x:Type CarsViewModel}"> <DockPanel> <Label DockPanel.Dock="Top">Cars</Label> <local:ItemView/> </DockPanel> </DataTemplate> </code></pre> <p>This is a cool idea for another reason. Right now, if you don't provide a data template, whenever WPF presents an object it creates a <code>TextBlock</code> containing <code>object.ToString()</code>. Implementing a generic base class gives you a way to globally override this behavior just by creating one data template, e.g.:</p> <pre><code><DataTemplate DataType="{x:Type ItemViewModelBase}"> <TextBlock Text="{Binding ItemName}"/> </DataTemplate> </code></pre> <p>That's not easier than just overriding <code>ToString()</code> to return <code>ItemName</code> (which is where I'd start), but if (for instance) you want a <code>ToolTip</code> that displays detailed information when the user mouses over it, you just add it to this one template and it works everywhere in your UI.</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