Please review to CAS-78926-JTBB92

They were able to recreate the problem and basically said "tough luck, change your code"

I was hoping someone else may have run into this problem, and had alternatives.

My alternatives are very costly right now.  I have over 10 million lines of customer code, and it will take a minimum of 40 hours just to review and identify any potential problems...  And, of course, my other concern, is what else has changed...

Do you have a detailed list of all changes for 11.1 and 11.2?  Normally, I only look at the high level items, but being able to read the detail, I could see if anything seems out of place.

 

Roger

Hi Roger,

rogerbundy said:

They were able to recreate the problem and basically said "tough luck, change your code"

I can certainly understand your frustration, but I looked up your case and I don't beleive that this is a fair characterization of what you were told.

Anyway, there seems to be some confusion here about the issue. This post here on the forums is talking about the SelectedIndex, but the sameple attached to your case is not using SelectedIndex, it's using SelectedItem. I can reproduce the issue with SelectedItem, so I assume that's just a mistake in the title of your forum post.

Infragistics Developer Support explained to you through your case that the change in behavior was the result of a bug fix and also to bring UltraComboEditor in line with the inbox ComboBox control, which also doesn't update the SelectedItem.

SelectedItem was not supposed to be changing while you type and this was causing problems in other areas, so that's why it was changed.

I think they release a list of all of the bug fixes in a particular version and it gets installed with NetAdvantage, but I could be wrong, that's not really my area. I know there's a Breaking Changes list, also, but I'm not sure this particular bug fix was on it.

It's very unfortunate that you have code that was relying on a bug in the control, but I'm afraid there's not much we can do there. Sometimes changes have to be made in order to fix existing bugs. That's just the reality of software.

Anyway, you have a couple of options here. I beleive Developer Support suggested that you move your code from ValueChange to SelectionChanged. That works when I try it with your sample, but I am not sure it's the best solution, since I don't think SelectionChanged will fire when you type in something that is not a match for anything on the list.

Another option would be to continue using the ValueChanged event and get the matching item from the list yourself, rather than relying on the SelectedItem property. You can use the IValueList implementation of the ValueList on the combo to make this easier.

    Private Sub UltraComboEditor1_ValueChanged(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles UltraComboEditor1.ValueChanged

        Dim selectedItem As ValueListItem = Me.GetSelectedItem(sender)
        Try
            TextBox1.Text = selectedItem.DisplayText.Substring(3, Len(selectedItem.DisplayText) - 3)
        Catch ex As Exception
            ListBox1.Items.Add(ex.Message & " ")
        End Try
    End Sub

    Private Function GetSelectedItem(combo As UltraComboEditor) As ValueListItem
        Dim valueList As IValueList = combo.ValueList
        Dim i As Integer = -1

        valueList.GetValue(combo.Text, i)
        Return combo.Items(i)
    End Function

Yes, selectedItem..

Reality is a tough concept. Getting eaten by a lion may be good for the lion, but I am sure I would not like it...

Thank you for your response.  You have given me an alternative that I can try.

 

Roger.

I finished the code for the ivaluelist, and it is working.

Thank you.

Roger.

Hi,

 

I just wanted to know if you were able to solve your issue based on Mike's suggestions or you still need help? Just let me know.

Thank you.