Hello,
I have a XamComboEditor whose ItemSource is bound to a list of KeyValuePairs. The DisplayMemberPath is bound to the value property, and the ValuePath is bound to the key. To give a specific example, there are two items in the list:
key=1 value="Debit"
key=-1 value="Credit"
What I want to do is programmatically set the value of the editor to 0 (i.e. not a valid value), have it display blank, and force the user to make a choice between the two valid selections. However, when I do this, the XamComboEditor displays "0". Am I missing something? Is there a way to get it to display blank in this case and give the user his two choices of Debit and Credit?
Thanks!
Bob
It looks to me like this control has some potentially useful features, but I have to figure out how to get by without a SelectedValuePath type of property. That complicates things a lot for my application; I really need to be able to bind the selected value to property in my viewmodel. Kinda frustrating that something that seems so basic (and that is in the WPF-specific version) isn't there already. Must invent a way around not having it only to have to undo it again when 14.1 comes out....
Thanks for your help.
I am just checking, if you need any further assistance on this matter.
Hello Bob,
Thank you for your reply. The XAML XamComboEditor is a cross platform control between WPF and Silverlight and we have added after adding the WPF specific one in our WPF packages. It provides some different options than the igEditors:XamComboEditor like multi selection and it is not an ItemControl and you cannot add items directly in XAML. It must be strictly bound to data. It is not extended version of the WPF Specific XamComboEditor.
In our upcoming Infragistics for WPF vol.14.1 we have added properties like ‘SelectedValue’ and ‘SelectedValuePath’ in the XAML XamComboEditor.
Let me know, if you need any further assistance on this matter.
I am looking at your sample application. Our use of XamComboEditor (again in LOTS of places in our application) relies on being able to bind its Value property to a property in our model. The XAML XamComboEditor does not have a Value property, so the way one has to implement it looks to be dramatically different from the WPF XamComboEditor. Am I missing something?
What is the difference between them (I understand one is WPF specific and the other is "XAML cross platform")? Will this break anything else? (I use the XamComboEditor all over the place in my application.) What are the reasons for using one version over the other in a WPF thick client (non Silverlight) application? Why are there two versions at all?