There is no uniform way to query dynamic properties, generally it’s expected that you know them ahead of time. With DynamicObject, implementers may override GetMemberNames and that generally gives you the properties, however it is really meant for debugging because there is no requirement that it provide all properties. Otherwise if it’s your own DynamicObject … Read more
Nevermind, I finally found out how the referenced code works and could come up with a solution. Here’s just a short explanation for the record. <TextBlock Text=”{t:Translate ‘import files’, {Binding FileCount}}”/> This requires a class TranslateExtension, inherited from MarkupExtension, with a constructor accepting two parameters, one String and one Binding. Store both values in the … Read more
You can’t bind using element name from a context menu. The link is broken between the context menu and its placement target. You can get around it using a couple of tricks though… Use RoutedUICommands with a command binding on the UserControl, then no binding is needed. Use the placement target binding on the context … Read more
Because DataGrid columns are abstract objects which do not appear in the logical or visual tree of your window. You cannot bind properties on them using ElementName (there will be no namescope which is needed for those bindings). You can try using Source and x:Reference instead, e.g. {Binding Source={x:Reference TextCol01}, Path=ActualWidth}
The declaration of your control and the instantiation are basically manipulating the same object, all the properties that are set in the declaration are also set on every instance. So if the properties were “visible” so to speak: <UserControl x:Class=”MyControlLib.ParentControl” xmlns=”http://schemas.microsoft.com/winfx/2006/xaml/presentation” xmlns:x=”http://schemas.microsoft.com/winfx/2006/xaml” xmlns:mc=”http://schemas.openxmlformats.org/markup-compatibility/2006″ xmlns:ctrl=”clr-namespace:MyControlLib”> <ctrl:ChildControl x:Name=”ChildName” DataContext=”{Binding RelativeSource={RelativeSource Self}}” PropertyOnChild=”{Binding PropertyInParentContext}”/> </UserControl> This is why … Read more
According to Samich’s answer, Here is a full example, the binding source is an Object private void Form1_Load(object sender, EventArgs e) { List<randomClass> lst = new List<randomClass>(); lst.Add(new randomClass()); lst.Add(new randomClass()); lst.Add(new randomClass()); lst.Add(new randomClass()); lst.Add(new randomClass()); lst.Add(new randomClass()); ((ListBox)this.checkedListBox1).DataSource = lst; ((ListBox)this.checkedListBox1).DisplayMember = “Name”; ((ListBox)this.checkedListBox1).ValueMember = “IsChecked”; for (int i = 0; i < … Read more
You can bind a byte[] to an Image. Here a Sample: Xaml: <Image Source=”{Binding UserImage}”/> Code: private byte[] userImage; public byte[] UserImage { get { return userImage; } set { if (value != userImage) { userImage = value; OnPropertyChanged(“UserImage”); } } }
Databinding errors are swallowed natively, but they are displayed in the OUTPUT dialog in the visual studio interface. If you wish to be notified (and have as much control over it as possible), then you can use Trace Sources. Bea Stollnitz provides a great writeup about this (and debuginng the bindings in general) here: http://www.beacosta.com/blog/?p=52 … Read more
ListChanged notifications for item value changes are only raised if the list item type implements the INotifyPropertyChanged interface. Taken from: http://msdn.microsoft.com/en-us/library/ms132742.aspx So my first question would be: Implements your item the INotifyPropertyChanged properly?
Unfortunately, what you want to do is not possible in XAML (from MSDN): Your custom class must not be a nested class. Nested classes and the “dot” in their general CLR usage syntax interfere with other WPF and/or XAML features such as attached properties.