According to your documentation the correct event to use to detect a change in value from the combobox is SelectionChanged.
This event is firing twice when the combobox is configured in the following way (irrelevant properties removed)
<ig:XamComboEditor Name="TestCombo" ItemsSource="{Binding DeviceTagValues}" DisplayMemberPath="Id" SelectedItem="{Binding SelectedDeviceTagValue, Mode=TwoWay}" AutoComplete="True" IsEditable="True" CustomValueEnteredAction="Allow">
When you have selected a different item in the list that has the same DisplayMemberPath value as the currently selected item the setter for the bound SelectedItem is fired twice (the SelectionChanged event is fired twice also)
Once to set it to the new value and then again setting it back to the previously selected value.
I believe this is a bug.
I have attached a solution that reproduces the issue. I am currently using v11.2.
I have been able to work around this issue in my solution somewhat by using a command that is invoked on the PropertyChanged event but this has a different bug where it doesn't select the new value. I believe this is because the DisplayMemberPath values are the same ,so a selection change is not detected.
What am I meant to do? Is it possible to separate what is dispalyed in the combobox when an item is selected from the DisplayMemberPath property? I.e Display A44 in the combobox where the value for DisplayMemberPath is A44,MG43.
This way the DisplayMemberPath values are different thus a selection change would be detected but the display in the combobox can be styled as needed.
To reproduce the issue in the sample I have attached complete the following steps
Please get back to me ASAP regarding possible solutions.
Hi,
this is bug for sure. I have submitted an internal bug item #100051. I've also created a support case on your behalf so you could track the progress on it. The support case id is CAS-82558-NP9NZ6.
Thanks for reporting the issue in such a clear and detailed manner. If you need any further assistance on this matter you could contact the Developer Support or write here as well.
Regards,
Has there been any update to this bug?
I have similar behavior using a regular ComboBox in a grid. When the selection is changed, it is fired twice for the same selection. This happens with two way binding on the grid. With one way binding it is only fired once. However, one way binding does not update the grid data.
I got an email about a month ago indicating that this had been addressed in the latest version but I have not tested it as the project I was working on finished some time ago.
Sorry to bother you in your thread, but I'm interested in knowing if this problems possibly persisted in event execution for things like templateClosed
Would someone have a clue about this issue?