> The problem is that the objects have different signatures (vmts or something). That means that a font in your dll will not > be recognised as a font by the calling program and vice versa. That starts to cause problems when you want to > dynamically add components to forms etc. That applies to all objects so you end up doing a lot of casting.
We didn't have this problem with fonts: I suppose it might be because the DLL's I was working on weren't using dynamically added components. I use dynamically added components myself quite often however: if I understand correctly, the problem arises when the DLL's visual component is "dropped" on the calling program's form: does the new component take on the parent forms font values or default values or what? By casting, I presume you mean assigning the font property values that you want on the new component _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
