Ed Leafe wrote:
+ I see now why you wanted to raise Hit when the value changed. I'd
suggest instead to revert that change and respond to ValueChanged
instead, which is the intent of that event.
This is the case only in dropdowns; on other list controls, you can
change the value without firing Hit.
Huh? You want dDropdownList to behave differently from other controls WRT Hit?
Oh, maybe you meant to say:
> This is the case only in dropdowns; on other list controls, you can
> change the value without firing *ValueChanged*.
ValueChanged should always fire when the value changes, whether through user
interaction or programatically. However, with most controls this will happen
only when the control loses focus (when flushValue() is called).
--
Paul McNett
http://paulmcnett.com
http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
