Ed Leafe wrote:
On Nov 10, 2005, at 3:58 PM, Paul McNett wrote:
The thing that Hit should do is whatever the main purpose is for that
control. With lists, you are selecting an item, and when you
double-click or press enter on an item, the item is selected, so a
Hit is generated. For dropdown lists, it is the same except just
moving to the item selects it. So, I think without looking at it the
controls are behaving correctly WRT Hit.
So do I. My point was that the purpose of the demo was to show two
different onHit_xxx() methods, and how the 'xxx' ties to the RegID.
And I think you shouldn't be doing onHit_ddList(), but onValueChanged_ddList(),
because you care about when the value changes, not how the value changed.
I agree, BTW. I just wanted to point out that it doesn't currently
work this way for all controls. In my mind, flushValue() should
happen immediately for all controls except dTextBox and dEditBox. Do
you agree?
Which controls besides the text-editing and list controls don't do
that?
I haven't taken an inventory, but AFAIK the only controls that flush immediately
are:
dCheckBox
dSpinner
Yep, however one could argue that that shouldn't happen in the same
callstack for performance reasons if you have lots of controls to
update, but yes I agree. Even if the controls aren't data-bound to
each other like in your demo, the ValueChanged needs to be raised
upon the value changing, so that if some other control is interested
in responding to that, it can.
Again, I'm not concerned with guaranteeing an optimized app. If we
write Dabo correctly, bad developers can still make crappy apps.
I'm not interested in guaranteeing an optimized app either...
--
Paul McNett
http://paulmcnett.com
http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
