I'm puzzled why the Change and CLick events are fired in reverse order, in an Excel ComboBox.
Here's a situation:
I have a ComboBox containing a list of items. In order to select one I click on the drop-down button, and then click on an entry in the list. At that point the entry is transferred to the text-box area of the control. So I've done two clicks. The events I would expect to see would be:
Instead, what happens is:
There is no member which allows the Change event to indicate that it has happened as part of an earlier Click. Of course, if you processed them in the order which I believe to be more sensible, then the simple fact of the Click event would allow me to save that event, and modify the processing in the Change event. (How much more wonderful if the ComboBox itself indicated the state of the list, which is really what we need to get).
Has anyone else experienced this problem? And if so, how have you solved it?