Hi, I don't think it's a matter of not being able to import a class from the loaded BPL as much as it probably hasn't been registerd properly with the RTL system.
I do something similar in a plugin architecture that I've developed using runtime packages. What I've done to get around this type of problem is that I have a single global unit that has a number of "helper" functions that both the main application and the plugin packages know about. One of these functions is RegisterPlugin and the plugins call this themselves after they've been initialized and they pass in the plugin object information. I use Interfaces and not classes but I don't think that should make a lot of difference. So when the runtime library is loaded I call one of the global helper routines to provide the proper information regarding the plugin and before the package is unloaded I call another helper routine to remove and clean up the necessary information. Once the information is registered with the global routines then I have access to those objects via the helper routines. Does that make sense? Ryan. ----------------------------------------------------- Home page: http://groups.yahoo.com/group/delphi-en/ To unsubscribe: [EMAIL PROTECTED] Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/delphi-en/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
