Dear
I'm facing with the problem of xamComboEditor in my Silverlight form. In the form I use ComboEditor as the filter for data source of data form. Everything are ok just only one problem when I click on other tabitem and then click back to tabitem has xamCombo, the xamCombo is set to blank. I try use standard combo of silverlight it has no problem. I also don't have any code for Tabcontrol event.
Please check my attached pictures for reference.
Pic1: Form loaded for the first time, everything ok
Pic2: change to other tabitem.
Pic3: back to the first tabtiem, the problem happen.
Thanks
Han
Thanks Konstantin Koynov
Hi Han,
I've submit an internal issue about this - 98944. I've also created a support case on your behalf which will be linked to the internal development issue so you could track the progress of this issue. The case number is CAS-81350-N9HF6H.
Regards,
I've managed to reproduce the issue you are describing. I'll investigate it further more and will replay back to you shortly.
Dear Konstantin Koynov,
Currently we need to upgrade to Silverlight 5 therefore we have to test our project with new version of xamComboEditor (InfragisticsSL5.Controls.Editors.XamComboEditor.v11.2, Version=11.2.20112.45).
The issue is happened as I submitted in the previous post. If xamComboEditor datasource is loaded from WCF the issue happen. If the xamComboEditor is loaded from xml it has no broblem.
I attached the test source, in this source I added 3 control:
1. xamComboEditor with data source from xml file
2. XamComboEditor with data source is loaded from wcf data source.
3. Standard ComboBox with data source is loaded from wcf data source.
The issue happened when we select any value for all Combo then click to the second Tab and then click back to the first Tab. The issue is happened to the second xamComboEditor, its content is clear while the orther is ok.
This source code I used Northwind database on local SQLServer for testing. If you want to test just modify connection string in web.config.
Please help me!
Thanks a lot for your response.
Finally I found the solution that is the problem only happen for version v11.1.20111.2054 so I changed back to the previous version v11.1.20111.1004. Now it has no problem.