Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><code>Chromosome</code> is your Model. Your XAML code resides in your View. The hypothetical "modified-length" value should reside in your ViewModel.</p> <p>You are correct in saying that making a new property for the modified height is not MVVM (and is a very bad idea generally, of course).</p> <p>For a better approach, you would normally put the modified-length property in the ViewModel. However your problem is now that your ViewModel has an <code>ObservableCollection&lt;Chromosome&gt;</code> and therefore cannot provide a simple modified-length property for each one of the <code>Chromosome</code> instances.</p> <p>Therefore, you have two choices:</p> <ol> <li><p>Implement a <a href="http://msdn.microsoft.com/en-us/library/system.windows.data.ivalueconverter.aspx" rel="nofollow"><code>ValueConverter</code></a> that translates the original <code>Length</code> to an appopriate <code>Grid.Height</code>. This could be either in your ViewModel or the View, but I think putting it in the ViewModel is not appropriate (since it will be used by a specific View only). This is the simplest approach.</p></li> <li><p>Wrap every <code>Chromosome</code> in its own ViewModel, e.g. <code>ChromosomeViewModel</code>. Your existing ViewModel would take a collection of <code>Chromosome</code>s and expose an <code>ObservableCollection&lt;ChromosomeViewModel&gt;</code>. You would then create a <code>ChromosomeView</code> bound to each ViewModel, which would basically be what you have now in your <code>ChromosomeDataTemplate</code>. Since the <code>ChromosomeView</code> will be bound to a <code>ChromosomeViewModel</code>, which in turn wraps a single <code>Chromosome</code>, you can now provide a "modified-length" property directly in your <code>ChromosomeViewModel</code>.</p></li> </ol> <p>If it's just for this, I suggest going with the <code>ValueConverter</code>. However, keep the second approach in mind for more complex scenarios.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhether to include view specific information in model
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJon
    1. USJon
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhether to include view specific information in model
      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. VTUpMod
    1. COIts just for this. I will encapsulate future collections in View Models.
      singulars
      1. PO
      1. USKiang Teng
 

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