🚀 go-pugleaf

Is it just me, is this thing broken?  I've tried the example of doing this
straight out of the Delphi Developer's Handbook (using RegisterCustomModule
and a TIExpert descendant to create the new form), and while the form will
show up with the new properties available, it simply refuses to add the
ancestor class' unit to the new unit.  While it's simple to fix, it's
annoying in the extreme, and it's hardly something I would want to
distribute to other developers (which is why I started looking into this to
begin with).

The only thing I found that works is Sergey Orlik's Custom Forms Pack
(CFPack), and it get's around the problem by implementing a custom
TIModuleCreator(Ex) to write the source code of the new unit.  I don't much
care for that since you can never be certain the default source for a new
form unit won't change between Delphi versions.

I've tried this under Delphi 3.02 C/S and 4.00 Pro, and both have the same
problem.  Is this just me, or is it why we don't see many people writing
and distributing custom forms?


Regards,
Brad
Free Delphi Stuff:  http://www.pobox.com/~bstowers/delphi/
My return address is intentionally invalid; delete ".Remove-This-Spam-Blocker" for real address