At 1:27 PM -0800 4/5/99, FPS, LLC - support wrote:
>Yes, but...
>
>Visually, it looks much better for the end user.
>
>I've tried it the other ways, and doing it pre FrmDrawForm just looks
>faster.
We're still left with the problem of who draws the form background--that
is, who erases the window. If you draw before FrmDrawForm, then
FrmDrawForm can't do it. ...and there's no other place.
You should not draw before FrmDrawForm.
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.
It would be up to you to figure out how to draw the gadget, but you could
do your own dispatching using data from the gadget. Not very C++, I admit,
but it only costs 4 bytes per form, and I think we might be able to manage
that.
An alternative solution would be to create a frmDrawObject event that would
get passed to the form's event handler. That's sort of nice because it
doesn't change any data structures and probably won't break any apps.
...but it's a lot more overhead, and I think it requires the form's event
handler to be reentrant.
Any more ideas?
--Bob
