🚀 go-pugleaf

"Dan Mayo" <dmayo@dickey-john.com> wrote in message
news:45b0d69a$1@newsgroups.borland.com...

> "Note: When working with form objects, do not explicitly call the
Free
> or Destroy method to free them. Instead, use the Release method,
which
> waits until all event handlers have finished executing."

Do not call Free() or Destroy() ('delete' in C++) while inside one of
the TForm's own event handlers.  That is the only place where you need
to use Release() if the form wants to free itself.  Otherwise, Free()
and Destroy() ('delete') work fine.

> Does this mean I should call "theDialog->Release();" rather than
> "delete theDialog;"?

There is nothing wrong with doing that in the code you showed.  Using
'delete' is the proper thing to do in that situation.

> Reading the "Release()" function call help the note appears
> contradictory to the TForm() section:
>
> "Note: Release returns immediately to the caller. It does not wait
> for the form to be freed before returning."

That is correct.  Release() posts a CM_RELEASE message to the message
queue.  The form is freed when the message is processed later on.
That allows any active and pending event handlers to finish running
before the form is freed.

> So does Release() wait for everything to be done first before
> returning to the next line in code?

No.

> Do I need to call both Release() and then delete?

No.  That will crash your code as the TForm will be freed twice.

> Is there something I should do to make sure that Release() has
> finished prior to calling delete?

Stop using Release() in this situation.  It does not apply at all.


Gambit