Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It may be more in line with MVVM to do 2 Views (data templates). Just do them as generics in the control resources.</p> <pre><code>&lt;TabControl&gt; &lt;TabControl.Resources&gt; &lt;DataTemplate DataType="EditorTabViewModel"&gt; &lt;Button Content="Enabled for Editor only" IsEnabled=True Command=SomeCommand /&gt; &lt;Button Content="Enabled for Preview only" IsEnabled=False Command=SomeCommand /&gt; &lt;/DataTemplate/&gt; &lt;DataTemplate DataType="PreviewTabViewModel"&gt; &lt;Button Content="Enabled for Editor only" IsEnabled=False Command=SomeCommand /&gt; &lt;Button Content="Enabled for Preview only" IsEnabled=True Command=SomeCommand /&gt; &lt;/DataTemplate&gt; &lt;/TabControl.Resources&gt; &lt;TabControl.ItemTemplate&gt; &lt;DataTemplate DataType="TabViewModel"&gt; &lt;TextBlock Text="{Binding SomeValueToShowAsHeader}" /&gt; &lt;/DataTemplate&gt; &lt;/TabControl.ItemTemplate&gt; &lt;/TabControl&gt; </code></pre> <p>So what happens is all the tabs have the same tab header, because the itemtemplate is explicitly defined. But because the ContentTemplates are not explicitly defined, when the control looks for a template for the content, it will give it the default template for the domain. Since we define 2 default templates, one for EditorTabViewModel and one for PreviewTabViewModel, when it comes across one of these, it will assign it to that data template. This should result in two different displays showing in the tab collection. I havent tried it fully with tab viewmodel so let me know if it doesnt work as expected.</p>
    singulars
    1. This table or related slice is empty.
    1. POC#/MVVM: Enable/Disable Buttons based on another control's property
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTerrorAustralis
    1. USTerrorAustralis
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COyes. this is the way I do it. But I think you misunderstood my question. This displays my `ViewModels`. I want to enable/disable buttons based on the type of `ViewModel` displayed and maybe attributes of controls within the `View`
      singulars
      1. PO
      1. USJiew Meng
    2. COBinding between controls is simple, just use `{Binding ElementName=otherControl, Path=otherControlProperty}`. And if you have two different views defined as above, then they should handle different types of ViewModels, so you could just set the buttons to enabled or not enabled on the different data templates
      singulars
      1. PO
      1. USTerrorAustralis
    3. COI roughly get the idea but can you give a fuller example? I am still abit lost :)
      singulars
      1. PO
      1. USJiew Meng
 

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