Databases
StackOverflow2013
Postsdbo
POwpf binding from child window
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POwpf binding from child window
    primarykey
    data
    text
    <p>I'm learning XAML and I'm having a problem binding content of a control to a settings property from a child window.</p> <p>Here's a quick example I've made to make it more clear. Calling the child from the main window:</p> <pre class="lang-vb prettyprint-override"><code>Private Sub Button1_Click(sender As Object, e As RoutedEventArgs) Handles Button1.Click Dim OwndWindow As New WindowChild OwndWindow.Owner = Me OwndWindow.ShowDialog() End Sub </code></pre> <p>And this is the child:</p> <pre class="lang-xaml prettyprint-override"><code>&lt;Window x:Class="WindowChild" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:src="clr-namespace:WpfApplication2" Title="WindowChild" Height="300" Width="300"&gt; &lt;Window.Resources&gt; &lt;ObjectDataProvider x:Key="ObjDatPro" ObjectType="{x:Type src:TestSettings}"&gt;&lt;/ObjectDataProvider&gt; &lt;/Window.Resources&gt; &lt;Grid DataContext="{Binding Source={StaticResource ObjDatPro}}"&gt; &lt;CheckBox Content="CheckBox" Margin="0" HorizontalAlignment="Center" VerticalAlignment="Center" IsChecked="{Binding Default.BoolSetting, Mode=TwoWay, UpdateSourceTrigger=PropertyChanged}"/&gt; &lt;/Grid&gt; &lt;/Window&gt; </code></pre> <p>At this point Visual Studio is reporting an error: <em>The name "TestSettings" does not exist in the namespace "clr-namespace:WpfApplication2".</em> (Line 7, Column 49)</p> <p>I've tried changing this part to <code>WindowChild.TestSettings</code>, but then VS complains that nested types are not supported.</p> <p>Changing CLR namespace to <code>WpfApplication2.WindowChild</code> or even <code>WindowChild</code> doesn't do the trick, VS says: <em>Undefined CLR namespace. The 'clr-namespace' URI refers to a namespace 'WindowChild' that could not be found.</em></p> <p>What am I doing wrong here?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USKaidan Alenko
    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. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POwpf binding from child window
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POwpf binding from child window
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POwpf binding from child window
      1. This table or related slice is empty.
      1. VTUpMod
    1. COtry this: xmlns:src="clr-namespace:WpfApplication2;assembly=WpfApplication2". If it doesn't help clean the Solution and Rebuild everything.
      singulars
      1. POwpf binding from child window
      1. USDilshod
    2. COI've finally figured it out: instead of using `<Window.Resources>` and `ObjectDataProvider` all it needed was `<Window.DataContext><src:TestSettings/></Window.DataContext>`.
      singulars
      1. POwpf binding from child window
      1. USKaidan Alenko
    3. COSince you figured it out yourself, you should write your own answer and mark this as answered!
      singulars
      1. POwpf binding from child window
      1. USTy Morrow
 

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