Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>So when you do this:</p> <pre><code>&lt;Window.Resources&gt; &lt;local:SelectWaferButtonViewModel x:Key="SelectWaferButton" /&gt; &lt;/Window.Resources&gt; </code></pre> <p>WPF will create a new instance of the <code>SelectWaferButtonViewModel</code> and add it to it's resources. You then bind to this by setting the <code>DataContext</code> using the <code>StaticResource</code> with the key. </p> <p>However, if you are then creating another <code>SelectWaferButtonViewModel</code> in your code behind and linking up your command to that instance, then it's not the same instance, so changes to the properties of this unbound instance won't effect your UI. There are a couple of ways around it. You can either a) create a single <code>SelectWaferButtonViewModel</code> in the code behind as a property and then bind to that in XAML, or b) Declare your <code>SelectWaferButtonViewModel</code> in XAML as you currently have it and then retrieve that instance in your code behind, like this:</p> <pre><code>SelectWaferButtonViewModel swbvm = (SelectWaferButtonViewModel)this.FindResource("SelectWaferButton"); </code></pre> <p><strong>Edit</strong>: So after seeing your last edit, if you want to go with a) then I would suggest you expose <code>btnSelectWaferViewModel</code> as a property in your <code>WaferTrackerWindowViewModel</code> and then bind to that property with the DataContext of your Window set to the <code>WaferTrackerWindowViewModel</code> instance. So you end up with something like:</p> <pre><code>&lt;DockPanel Name="tvwDockPanel" Width="225" Visibility="{Binding MyButton.IsControlVisible, Converter={StaticResource BoolToVisConverter}}" DockPanel.Dock="Left"&gt; &lt;/DockPanel&gt; </code></pre> <p>and:</p> <pre><code>public class WaferTrackerWindowViewModel :INotifyPropertyChanged { private SelectWaferButtonViewModel btnSelectWaferViewModel; public SelectWaferButtonViewModel MyButton { get { return btnSelectWaferViewModel; } set { btnSelectWaferViewModel = value; OnPropertyChanged("MyButton"); } } //...... </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POMVVM Binding Issue - Another Noob-ish Issue
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMatt Burland
    1. USMatt Burland
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMVVM Binding Issue - Another Noob-ish Issue
      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
    1. COI tried this and what I am finding is when this method gets called: private void ExpandPanel() { btnSelectWaferViewModel.OnButtonClick(); } btnSelecteWaferViewModel object is null, which is odd. The problem is, after initialization, when the command fires, it uses a different object of the WaferTrackerWindowViewModel than the datacontext was set to in the code behind. I have no idea why this is, but I break after the command fires and I see everything in the WaferTrackerWindowViewModel class is set to null
      singulars
      1. PO
      1. USkformeck
 

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