I have UltraCombos that I bind at run time with a datatable. In the latest release (2034), the ValueChanged event does not fire when the selected row is cleared.
In version 11.1.20111.2026 and previous versions this worked as expected. When the selected value is clear the ValueChanged event fires. This started happening right after the upgrade to 11.2.20112.2034 with no other code changes.
Can you confirm this as a bug or are there additional settings that must be set for changing the value to nothing to fire the ValueChanged event?
Hi,
What exactly do you mean when you say "the selected row is cleared." Can you post a small sample project or even some code that shows exactly what you are doing to clear it?
Here is my code to fill the combo with data:
With cboAddressType .DisplayMember = "AddressType" .ValueMember = "AddressTypeId" If modCodePal.gbMadminUser OrElse modCodePal.NoMadminUser() Then oSQL = "Select AddressType, AddressTypeId FROM AddressTypes Order By AddressType Asc" Else oSQL = "Select AddressType, AddressTypeId FROM AddressTypes Where (AgencyId='" & modCodePal.gstrAgencyId & "' OR AgencyId IS NULL) Order By AddressType Asc" End If .DataSource = eData.GetDataTable2(GetConnectionString, oSQL) SetDropDownWidth(cboAddressType, "AddressType") .SelectedRow = .Rows(0) End With
When the form is open, I select the text that is in the display area of the combo and hit delete. In previous version, this fired the ValuedChanged event for the combo. In the latest (11.2.20112.2034) the ValueChanged event no longer fires when I hit delete nor when I tab off of the control after deleting the contents.
The combo box has had the value set to Nothing but the ValueChanged event has never fired.
Hello Paul,
I have created case # CAS-88549-74D6SZ for you to better assist you with this issue going forward. To access the case, simply log into your IG account and click on My Support Activity.
I am also running into this issue. Is there a hotfix or update that resolves this issue yet?
Hello,
I will be happy to help you out with this issue.
I have created case # CAS-85719-S2XJX for you to better assist you with this issue going forward. To access the case, simply log into your IG account and click on My Support Activity.
Please let me know if you have further questions in this matter utilizing the case created.
Thank you for your quick reply!
I tried this out and I get the same results.This is clearly a bug and needs to be corrected.
I have forwarded this thread and a sample over to Infragistics Developer Support so they can create a case for you and write this up for developer review. You should be hearing from them shortly with a case number.