Hi,
I have recently updated to what I think is your latest release (11.2.20112.45) and it seems to have introduced some weird behaviour into the dropdowns.
1. If you click into a dropdown and open the popup, but don't select any items, close the popup and then tab to the next field, the dropdown selects the first item in the list.
2. You can never select anything other than the first record in the dropdown. Everytime I select something different it reverts back to the previous selection when tabbing out.
I even encountered this behaviour in a sample application that you guys sent me after upgrading it to the latest release.
Is there something I need to do to stop this behaviour occuring?
Thanks.
Hello drdonna,
I have created two support tickets for you in order to link the development issues related to the XamMultiColumnComboEditor so you will be notified when the issues are resolved. I have linked the development issues ID of 100844 to support ticket with number CAS-83609-G8VLV6 and development issues ID 100843 to case CAS-83610-CY0LPM.
If you have any further question please do not hesitate to ask.
Sincerely,
Krasimir
Developer Support Engineer
Infragistics
www.infragistics.com/support
No it has just been reported and will be fixed in the next Service Release which will will be out in the beginning of March.
As Calsy has mentioned the problem occurs only when the CustomValueEnteredAction is set to "Add".
I'll ask our Developer Support team to create a support case for this and provide any further assistance on the matter.
Regards,
Has this been fixed? I may have to go back to just the combo box unless this has been fixed. It makes this control unusable.
Hi Calsy,
I've managed to reproduce both issues and submitted internal bug items for them(although I think the root cause is the same) the bug items are #100843(Issue 1) and #100844(Issue 2). I've also created a support case on your behalf - CAS-83486-Q34PZF so you could be notified when the fixes are released.
Thank you for taking the time to report these issues and in a such clear manner.
Hi Konstantin,
I've just been doing some more testing and the issue only presents itself when you set the CustomValueEnteredAction to Add, as it is in my sample project.