visual-tree

In a WPF app I want to move a UserControl from a ContentControl to another one in code: myContentControl2.Content = myUserControl; in this case I get an error: Specified element is already the logical child of another element. Disconnect it first. In a ControlControl class description I can see a RemoveVisualChild method , but when I try to use it in code I get an Unknown method error myContentControl1.RemoveVisualChild(myUserControl);//here I get an "Unknown method" error Where am I wrong? How to move a UserControl from a ContentControl to another one in code-behind? Set myContentControl1

I would like to have a WPF container (panel, user control, etc.) that exposes a property to turn all children to read-only if set. This should pretty much be like setting a parent control to IsEnabled=false, which also disables all children. What children and which of their properties should be considered is fixed (e.g. TextBox.ReadOnly, DataGrid.ReadOnly, ...). I have tried to create such a control, which essentially iterates all children of the visual tree (recursively) and deals with the controls accordingly. This works fine, except for the case where further changes would affect the visual

I have a C# Store App and using DataTemplate Selectors to determine which type of Template to use in a ListView Control bound to an Array. Because it is templated, I cannot assign a dynamic x:Name to each ListView Row. I need to be able to access the listview rows by Index and set the Visibility of them to On or Off. I have tried things like this, but the .ItemContainerGenerator .ContainerFromItem(item); return null and I get a Nullable exception every time: How do I access a control inside a XAML DataTemplate? After doing some research, it appears that the above solution only works if I touch

Having {Binding ElementName=foo} , will it lookup visual or logical tree? Of logical and visual trees in WPF | Data See, Data Do When does the logical tree matter? When looking up a name, such as in {Binding ElementName=Foo}, the search walks up the ancestry looking for a name scope, again just as it does for inheritable properties. ElementName binding in Silverlight via Attached Behaviours In order to enable this, WPF provides ElementName and RelativeSource bindings, giving you a powerful mechanism for locating other elements within your visual tree to bind to EDIT: It looks like the Logical