At 5:53 PM -0800 4/5/99, Kenneth Albanowski wrote:
>On Mon, 5 Apr 1999, Bob Ebert wrote:
>
>> I like the idea of having a callback mechanism. Probably we could make do
>> with just one call-back hook that gets called once before any form stuff
>> was drawn but after the erase, once for each gadget, and once after all the
>> form stuff was drawn.
>
>We've done without callbacks so far (except for the sort functions and the
>form handler functions),
... and table drawing functions, and table loading functions, and list
loading functions ... There is precedence. :)
>and I think I'd like to see it stay that way. But
>maybe we could get a new set of events for gadgets, or a new event filter
>function that makes it easy to generate events for gadgets.
So you don't think having the event handler be re-entrant would be a
problem? (Your form event handler calls FrmDrawForm, which would then
call-back into the event handler to handle drawing the gadget. It's either
that or gadget drawing is deferred until the next pass of the event loop,
which doesn't solve this problem.)
Anyway, I'm not sure if all those events are completely necessary. Most of
that stuff can be handled through existing form events. Drawing at the
right time is a significant problem, and I think hit testing, visibility,
etc. could use a little more support, but that's about all I was
envisioning.
For the list in general: (I don't want to open up a huge can of worms
here, so try to be conservative) What's in the way of effectively using
gadgets right now?
--Bob
