When you change the SelectedItem in the editor it sets the bound property multiple times.
It sets it to null and then it sets it to the value that was selected.
If an item is selected and the user sets focus on the control and then tabs out of the control without changing the item then the bound property is set to null and then to the item displayed.
This behaviour is creating a problem for me because I can't ignore null values. If I put a test for the value being null and ignore it, it is all ok, but unfotunately I need to perform certain actions if the user clears the selected item (sets to null).
This means I have no way of knowing whether the item was set to null due to the control behaviour or was actually set to null by the user.
I would consider this a bug.
I would have thought that if the user hasn't changed the selected item then the binding of SelectedItem should not be update either.
When the user changes the value from one item to another I woudl have thought there would be one binding update from the old value to the new. Not from the old value to null then to the new.
The standard silverlight combobox does not behave in ths manner. The SelectedItem only gets set when it actually changes
Even when I turn AllowFiltering and IsEditible off so that it is like a standard combobox it still sets it to null and then to the item the user selected.
This is definitely a bug.
This is a show stopper for me at the moment
Hi,
what version/build of the controls are you using? There was similar bug that was fixed some time ago.
Could you please provide sample xaml of your XamComboEditor setup so I could be able to check if I can reproduce this?
Regards,
I am using the latest trial version that I downloaded about a moth ago. I am pretty sure it is version 10.3
The company that I am consulting for have a full license and I have downloaded the trial version
As for a sample use the sample listed at
http://blogs.infragistics.com/forums/p/48422/272985.aspx
Just to confirm the version here is the test from my download email
Dear Tim Schneider,Thank you for visiting Infragistics.com and requesting the NetAdvantage for Silverlight Line of Business 2010 Vol. 3 : Bundle [Silverlight 3.0] download. Below you will find the download you requested.
Hi Tim,I've manage to reproduce the issue you are experiencing. As far as I was able to isolate the bug it seams that it is reproducible when IsEditable="True" and DisplayMemberPath property is not set. So you could try to use/set this prop as a workaround.
However, I've logged a bug item with internal id 78643 and created a support case on your behalf - Case ID: CAS-66782-1414KX where you could track the progress on the issue and be notified when the fix is done and a Service Release containing it is released.
Please let me know if you need any more assistance.
Ok thanks. In my solution I have DisplayMemberPath set but I need IsEditable to be true so that I can autocomplete/filter the items.
Thanks for looking into this so quickly.
binding to collections of strings(simple types i.e. int, double, etc.) is not supported. Could you try if this behavior is reproducible when binding to a collection of complex type?
Looks like this is not fixed in 11.1 version. I am using the latest version (11.1). I am binding the list of strings to the comboeditor box and IsEditable= true. Do i have to set displaymemberpath?
I have verified that this has been fixed in the 11.1 release. I will find out what license details the company I am consulting for has and see if they have access to the latest version. If they don't then I will contact the support team for the patch to 10.3.
Thank you for your quick resolution of this issue.
if you have DisplayMemberPath set and IsEditable=true and you still encounter this issue you could try to install the latest service release of 10.3 in order to get the fix that was made to the similar issue I've mention. Basically if you don't have a build including that fix the workaround i suggested might not be working.
In order to get the SR(patch) for 10.3 you need to contact the out Developer support team and request the patch. If you want just to test if the workaroud works you could download the 11.1 release and test with it - the fix should be included in it.
HTH