[RESOLVED] Select Case Control

[sgrya1]

Is it possible to Select Case by the control

    Sub ComboBox_SelectedIndexChanged(sender As Object, e As EventArgs) Handles ComboBox1.SelectedIndexChanged, ComboBox2.SelectedIndexChanged
 
        'This works
        If sender Is ComboBox1 Then
        End If

        'This doesn't
        Select Case sender
            Case ComboBox1
        End Select

        'And neither does this
        Dim myComboBox = DirectCast(sender, System.Windows.Forms.ComboBox)
       Select Case myComboBox
            Case ComboBox1
        End Select
    End Sub

[Shaggy Hiker]

You only have two options, so Select Case is perhaps a bit of a reach. Still, did you go out on a limb and try:

Select Case Sender
 Case Is ComboBox1
End Select

[sgrya1]

I get a "Rational operator expected" error on Case Is ComboBox1

[dday9]

I would setup the select/case to compare the control's name:

Select Case sender.Name
    Case ComboBox1.Name
        ' etc...
End Select

[sgrya1]

That's it. Thank you so much.
Intellisense doesn't bring up .Name on either of those.

[dday9]

Sender at that point would still be object, you should explicitly cast it to a control:

Select Case DirectCast(sender, Control).Name
    ' ...

[sgrya1]

Hard to explain but a picture might help. I can't implement what you suggested.
Attachment 183016

[sgrya1]

Sorry.Attachment 183017

[Shaggy Hiker]

Yeah, attachments have issues, as you can see.

Sender is a control, so you can cast to that. Still, I like my answer better. If you look at the answers in this SO thread:

https://stackoverflow.com/questions/...type-in-vb-net

You'll find that the question is not quite the same as what you are asking for, as they are trying to switch on the type, which wouldn't work for you at all, since the types are the same. However, you will also find an example of what I suggested as the third answer, and that should work for you.

[jmcilhinney]

This question is just wrong from the outset. The whole point of using a common event handler is to do the same thing for multiple objects. If you are trying to differentiate between the different objects that might raise the event then you shouldn't be using a common event handler in the first place. If you want to do one thing for ComboBox1 and something else for ComboBox2 then use two different methods to handle the event for the two different ComboBoxes. If you want to do partly the same thing and partly something different then put the part that's the same in a method and then call that method from both event handlers.

[Shaggy Hiker]

That's a good point. I overlooked that.

[dday9]

I too couldn't see the forest from the trees.

[jmcilhinney]

That's a good point. I overlooked that.

I too couldn't see the forest from the trees.

There may well be a situation where the question is valid, so knowing the answer is not a bad thing. This just isn't that situation.