Re:Design time vs run time packages
Quote
"Simon" <macneall@iinetdotnetdotau> wrote in message
news:Xns928254BEBE08Cwooohooo@207.105.83.65...
Quote
> So my question, can I statically link to the property editors?
No, and in fact you're explicitally not allowed to in BCB6. All property
editors must reside in separate designtime packages specifically so that
they won't be linked into the runtime project itself.
Components need to be segregated into separate runtime and designtime
packages, where the runtime package contains the component code itself only,
and the designtime package contains everything else that the IDE itself
needs in order to work the component (editors, pallete icons, registrations,
etc).
If you can't separate the code correctly, then you're going to find it
difficult to use that component.
Start with the original package, and just comment out the design editor
header file(s). Then try to compile. Everything that fails to compile,
move to a separate package. Then move the Register() function over as well,
and any icons and such as well. Everything that is left over should be just
the component code itself.
Quote
> And if not, I have read on the news groups that this
> component should actually be in 2 packages, one a
> runtime one with just the application code, and one a
> designtime one that extends the runtime component
> to add property editor stuff.
Correct.
Gambit