New Visual Studio 2010 WinForms C# project and imported existing form containing IG 2009 controls, which were updated to NetAdvantage 2011.
Our practice and existing code would always first our UltraCombo's datasource = null; before setting the datasource = datatable object returned from a SQL procedure call.
I was shocked to see that if the UltraCombo was already bound to a datatable, the calling of the same method to set a datasource is firing the RowSelected event of the combo when combo.datasource = null; is executed!
Needless to say, this is wreaking havoc in the project and we're looking for direction.
Is this a bug or something new in 2011??
Thanks!
Hi,
I tried this out and I am not seeing this behavior. If I have an UltraCombo with a selected row and I set the DataSource to null, RowSelected does not fire at that point. It does fire when I set the DataSource to something new, though - if the same value it previously had matches up to something on the new list.
This is correct behavior, since the actual Row object is different, even though the Value and text are the same.
I am attaching my sample project here so you can check it out. If I run the sample and click the button, the RowSelected event does not fire. This is correct, since there was no selected row to start with and changing the DataSource has no effect on that.
If I select a row and then click the button, the RowSelected event fires once. This is also correct since the original selected row was destroyed and a new row was created which happens to match the existing Value of the control (the Key field).
Hi Mike,
Thank you for the response and code. More specifically, I have 4 combo controls. I will refer to them as c1, c2, c3... Some event sets c1's datasource = datatable. The row selected event on all of the combos is set to load a datatable to the next combo in-line. This code has been in Production for several months, again as a Visual Studio 2008 project and NetAdvantage 9.
Workflow: User selects a value from c1 and a method is called from c1’s row selected event to set c2, c3 and c4’s datasource to null (to clear them) then c2’s datasource to a new datatable relevant to the value selected in C1. User then selects a value from c2 and c2’s row selected event calls a method to set c3 and c4’s datasource to null, then c3’s datasource is set to a new datatable, etc. The user can elect to have values selected in just c1 or all 4 combos. It depends on the amount of filtering they want to set for an eventual button click to return data to a grid.
So it appears that the row selected event does not automatically fire when the combo's datasource is set in version 9, but now does in v 2011? If this isn’t the case, I am willing to concede that I have no clue how to properly code this workflow. Again, what I have has been working perfectly in the Visual Studio 2008 project with 9.2 controls. I cannot get it to work the same in Visual Studio 2010 and 2011 controls. My latest iteration is leaving each combo with the previously selected value regardless of what value they select. It has been one of those weeks... :(
Hi Michael,
Yes, sorry. I responded only to the case for this post (CAS-78720-GHHPF4). I will close this post as there are two solutions. Here is that text from the case:
I was able to quickly reproduce the issue, which turn out to be the same issue just found this morning in my other post "Unexpected behavior changes between 9.2 and 11.2?".
Michael S. In your sample, simply change Combo2's .Value member to "State". Because three of the records have "NJ" as their State, when Combo2 loses focus "Jersey City" is left in Combo2 as the selected record even if you select "Newark" or "Trenton". This is the smoking gun and does not happen for us in our current production application using 9.2. Changing the .Value and .DisplayMemeber to "City" is the equivalent of what I need to do to "fix" our upgraded 11.2 application.
The new property you mention also fixes the issue, is the better solution, and turns to fix a larger issue I was having with another UltraCombo, which I am unable to replicate using your sample.
[Michael S.] "Try setting the "ItemMatchingMode" property of ultraCombo2 to "ValueListItemMatchingMode.DoNotConvertDataValueToString"."
At this point I am good to go. Is there any documentation that can be shared regarding the new (to us / post 9.2) Combo property ItemMatchingMode?
[Michael S.] http://help.infragistics.com/NetAdvantage/WinForms/current/CLR2.0/?page=Infragistics2.Win.UltraWinGrid.v11.2~Infragistics.Win.UltraWinGrid.UltraDropDownBase~ItemMatchingMode.htmlThanks to everyone who helped me resolve this issue!
Jaime,
Did you try my suggestion?
In the sample that you are referring to try setting the "ItemMatchingMode" property of ultraCombo2 to ValueListItemMatchingMode.DoNotConvertDataValueToString
I will update the case notes with these findings. I do not know if it is appropriate to link case numbers in this forum for Mike S. to see, or would it be best for you to attach the sample from the case?
Thank you Micheal S. and Mike S.
This post was elevated to a Support Case, so I now have examples from both of you. This morning I was able to modify an example for another forum post of mine dealing with a single UltraCombo to reproduce that issue, which looks like the non-unique column I set as the Combo's .Value is causing that issue, which is not an issue with the current production application running 9.2.
I will work on one of your samples now to see if I can replicate this issue with the chained Combos.
Thanks again, Jaime