M
Matthew Wells
Good Morning All,
I have a simple WinForm with a ComboBox at the top bound to a datatable.
It's set as a DropDown. When a selection is made it fires the
"SelectedIndexChanged" event. No problem. But when a user manually makes
the text blank, that event doesn't fire. Okay, I added the "TextChanged"
event to catch that. So when a user blanks out the text of the combobox,
the TextChanged event fires, I check to see if the text == "" and if so then
fire then fire the SelectedIndexChanged event. This works fine on the first
form I made.
I have a new form with the exact same setup. However, when the TextChanged
event fires after the text is deleted, the first line is
if ("" == DDApplications.Text)
which is false?
when I hover over DDApplications.Text, it shows the previous value, not ""
even though I can see on the screen it's "".
This still works fine on the first form.
Both comboboxes have the exact same properties - including the name.
All events have the exact same code - I copied it.
Any ideas?
Thanks
-- Matthew Wells
(e-mail address removed)
I have a simple WinForm with a ComboBox at the top bound to a datatable.
It's set as a DropDown. When a selection is made it fires the
"SelectedIndexChanged" event. No problem. But when a user manually makes
the text blank, that event doesn't fire. Okay, I added the "TextChanged"
event to catch that. So when a user blanks out the text of the combobox,
the TextChanged event fires, I check to see if the text == "" and if so then
fire then fire the SelectedIndexChanged event. This works fine on the first
form I made.
I have a new form with the exact same setup. However, when the TextChanged
event fires after the text is deleted, the first line is
if ("" == DDApplications.Text)
which is false?
when I hover over DDApplications.Text, it shows the previous value, not ""
even though I can see on the screen it's "".
This still works fine on the first form.
Both comboboxes have the exact same properties - including the name.
All events have the exact same code - I copied it.
Any ideas?
Thanks
-- Matthew Wells
(e-mail address removed)