Hence the FR. Even 4D has had this ability for well over a decade and they proved extremely useful ( even though 4D sucks these days imo ) so it cant be that difficult to implement.
On 12/4/07 23:49, "Norman Palardy" <[EMAIL PROTECTED]> wrote: > > On Apr 12, 2007, at 4:34 PM, Daniel Stenning wrote: > >> On 12/4/07 22:53, "Norman Palardy" <[EMAIL PROTECTED]> >> wrote: >> >>> >>> You could use dlopen / dlclose / dlsym to get the pointer and you >>> dont need to do a lot of extra work. >>> But you have no way to call it from within RB. >>> >>> You could write a plugin that would load the dylib and provide an >>> interface to the loaded routine. >> >> The problem isnt loading the plugin DLL or API etc, or getting the >> function >> pointer or opening/loading the library, it is finding a way to call >> the >> function that any function pointer refers to. RB allows one to set >> up and >> pass a function pointer based on an RB function ( callback ) to a >> declare >> function. My FR is just basically requesting the converse. >> >> Both are needed - >> >> A) the ability for a library or RB plugin to be able to invoke a >> callback >> inside an RB App >> >> B) the abiity to invoke a callback inside library or RB plugin itself. > > A declare into a library would work IF you could dynamically tell the > system what library to use > > But you can't so a plugin is probably required > > _______________________________________________ > Unsubscribe or switch delivery mode: > <http://www.realsoftware.com/support/listmanager/> > > Search the archives: > <http://support.realsoftware.com/listarchives/lists.html> > Regards, Dan _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
