On Nov 10, 2005, at 3:28 PM, Paul McNett wrote:
Huh? You want dDropdownList to behave differently from other
controls WRT Hit?
It already does, based on the changes we made a few weeks ago.
For list boxes and such, Hit only fires when you double-click or
press Enter on them. Dropdowns fire Hit when you select a new value.
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).
When you scroll through a list, the value changes without losing
focus. flushValue() should certainly be called in these cases, since
other controls depend on the list. Imagine a list box with client
names, along with several fields with client info. As you scroll
through the list, with focus remaining on the list, shouldn't the
controls update as the client changes?
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
