> I've changed my mind. This is not really the solution I need.
>
> The two problems with this are:
>
> 1) TComponentEditor does not have a handle so sending a user message to
> close the editing form is not straightforward.
>
> 2) Now the editing form has to keep a private handle to a component editor
> (set by the component editor when it created the editing form). ie. The
> editing form knows about the component editor (not ideal).
>
> The real problem is number 1. (2 is just an "in an ideal world...").
The correct solution is to use a Component Designer, not a Component Editor.
A designer is decended from TDesignWindow and acts like the dataset
designer, the standard Delphi list designer, the menu designer and other
windows that float about the designer 'tied' to a particular components.
How you go about this is very much more complicated than a component editor,
but any good Delphi text should have most of the information you need. My
recommendation is Ray Lischner's books, but other may have the information
as well.
If you need an good example to work from you could always buy our Fields
Editor which handles all of this stuff for D3 and D4 and work from there 8-)
Cheers, Max.
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
