Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Well, it would be easier if your element hierarchy was more like...</p> <pre><code>&lt;node type="forest"&gt; &lt;node type="tree"&gt; ... </code></pre> <p>...rather than your current schema.</p> <p>As-is, you'll need 4 <code>HierarchicalDataTemplate</code>s, one for each hierarchical element including the root, and one <code>DataTemplate</code> for <code>leaf</code> elements:</p> <pre><code>&lt;Window.Resources&gt; &lt;HierarchicalDataTemplate DataType="forestPad" ItemsSource="{Binding XPath=forest}"&gt; &lt;TextBlock Text="a forestpad" /&gt; &lt;/HierarchicalDataTemplate&gt; &lt;HierarchicalDataTemplate DataType="forest" ItemsSource="{Binding XPath=tree}"&gt; &lt;TextBox Text="{Binding XPath=data}" /&gt; &lt;/HierarchicalDataTemplate&gt; &lt;HierarchicalDataTemplate DataType="tree" ItemsSource="{Binding XPath=branch}"&gt; &lt;TextBox Text="{Binding XPath=data}" /&gt; &lt;/HierarchicalDataTemplate&gt; &lt;HierarchicalDataTemplate DataType="branch" ItemsSource="{Binding XPath=leaf}"&gt; &lt;TextBox Text="{Binding XPath=data}" /&gt; &lt;/HierarchicalDataTemplate&gt; &lt;DataTemplate DataType="leaf"&gt; &lt;TextBox Text="{Binding XPath=data}" /&gt; &lt;/DataTemplate&gt; &lt;XmlDataProvider x:Key="dataxml" XPath="forestPad" Source="D:\fp.xml"&gt; &lt;/XmlDataProvider&gt; &lt;/Window.Resources&gt; </code></pre> <p>You can instead set the <code>Source</code> of the <code>XmlDataProvider</code> programmatically:</p> <pre><code>dp = this.FindResource( "dataxml" ) as XmlDataProvider; dp.Source = new Uri( @"D:\fp.xml" ); </code></pre> <p>Also, re-saving your edits is as easy as this:</p> <pre><code>dp.Document.Save( dp.Source.LocalPath ); </code></pre> <p>The <code>TreeView</code> itself needs a <code>Name</code> and an <code>ItemsSource</code> bonded to the <code>XmlDataProvider</code>:</p> <pre><code>&lt;TreeView Name="treeview" ItemsSource="{Binding Source={StaticResource dataxml}, XPath=.}"&gt; </code></pre> <p>I this example, I did <code>TwoWay</code> binding with <code>TextBox</code>es on each node, but when it comes to editing just one node at a time in a separate, single <code>TextBox</code> or other control, you would be binding it to the currently selected item of the <code>TreeView</code>. You would also change the above <code>TextBox</code>es to <code>TextBlock</code>s, as clicking in the <code>TextBox</code> does not actually select the corresponding <code>TreeViewItem</code>.</p> <pre><code>&lt;TextBox DataContext="{Binding ElementName=treeview, Path=SelectedItem}" Text="{Binding XPath=data, UpdateSourceTrigger=PropertyChanged}"/&gt; </code></pre> <p>The reason you must use two <code>Binding</code>s is that you cannot use <code>Path</code> and <code>XPath</code> together.</p> <p><strong>Edit:</strong></p> <p>Timothy Lee Russell asked about saving CDATA to the data elements. First, a little on <code>InnerXml</code> and <code>InnerText</code>.</p> <p>Behind the scenes, <code>XmlDataProvider</code> is using an <code>XmlDocument</code>, with it's tree of <code>XmlNodes</code>. When a string such as "stuff" is assigned to the <code>InnerXml</code> property of an <code>XmlNode</code>, then those tags are really tags. No escaping is done when getting or setting <code>InnerXml</code>, and it is parsed as XML.</p> <p>However, if it is instead assigned to the <code>InnerText</code> property, the angle brackets will be escaped with entities &amp;lt; and &amp;gt;. The reverse happens when the value is retreived. Entities (like &amp;lt;) are resolved back into characters (like &lt;).</p> <p>Therefore, if the strings we store in the data elements contain XML, entities have been escaped, and we need to undo that simply by retrieving <code>InnerText</code> before adding a CDATA section as the node's child...</p> <pre><code>XmlDocument doc = dp.Document; XmlNodeList nodes = doc.SelectNodes( "//data" ); foreach ( XmlNode node in nodes ) { string data = node.InnerText; node.InnerText = ""; XmlCDataSection cdata = doc.CreateCDataSection( data ); node.AppendChild( cdata ); } doc.Save( dp.Source.LocalPath ); </code></pre> <p>If the node already has a CDATA section and the value has not been changed in any way, then it still has a CDATA section and we essentially replace it with the same. However, through our binding, if we change the value of the data elements contents, it replaces the CDATA in favor of an escaped string. Then we have to fix them.</p>
    singulars
    1. This table or related slice is empty.
    1. POTwo-way binding of Xml data to the WPF TreeView
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJoel B Fant
    1. USJoel B Fant
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POTwo-way binding of Xml data to the WPF TreeView
      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. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks Joel, that works. One question though. I surround the content in the data element with a CDATA section so that it is possible to store Xml. Is there a way to control how the XmlDataProvider writes out the data element?
      singulars
      1. PO
      1. USTimothy Lee Russell
    2. COIf there is XML as a string, it would escape angle brackets with entities (they start with &). This can be reversed because the Document property returns an XmlDocument. I'll edit and add the code for doing CDATA in the data elements.
      singulars
      1. PO
      1. USJoel B Fant
    3. COGreat -- that works. The performance is really bad for the size of documents that I am working with but instead of updating every node, I will add an IsDirty flag and only update nodes that have been edited.
      singulars
      1. PO
      1. USTimothy Lee Russell
 

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