DLL usage in RunRev

Alessandro Manotti ale870 at gmail.com
Mon Nov 28 02:23:49 CST 2005

Thank you for suggestions and links ;-)

But I noticed a bit of confusion about this argument (inside forum and
mailing-list, and RunRev documentation).

I will try to be more specific.

Please read the this (from mailing list):

Hi Eric,

here's the script from MetaCard's stack components...

on mouseUp
  local f
  if the platform is "Win32"
  then put "*.dll" into f
  else put "*" into f
  answer file "Choose an external:" with "external" with filter f
  if it is not empty then
    set the itemDelimiter to "/"
    if field "List" is not empty
    then put return after field "List"
    put the last item of it after field "List"
    set the externals of stack the label of button "Stack Name" to field
  end if
end mouseUp


Author says it functions correctly.
But the RunRev documentation about "externals" suggests to close
(destroy) and open stack.

What's the right procedure (how to use externals and close/open stack
without loosing externals configuration)?

let's suppose I need to use a generic DLL (not RunRev specific). And
let's suppose this dll is already registered.
Can you suggest the the smartest method to register and use it?

I tried to use some windows dll (just to try) using the previous code,
but nothing happened (only errors...). My second problem is I have not
a dll to test (my application must be able to use any dll, based on a
script supplied from another program...).

So... can you suggest me a proven method to use a generic windows dll?

Last item (I'm sorry): and about ".so" Linux files? Or Linux dynamic library?

Thank you in advance for your help!


On 11/28/05, Ken Ray <kray at sonsothunder.com> wrote:
> On 11/27/05 5:12 AM, "Alessandro Manotti" <ale870 at gmail.com> wrote:
> > Hello,
> >
> > can someone help me to understand how to use a Windows DLL in RunRev?
> Allesandro, we just went over this topic a few weeks back. It's detailed in
> the tip at my site:
> http://www.sonsothunder.com/devres/revolution/tips/ext002.htm
> Basically an DLL is either built exclusively for Revolution using the
> headers/source provided in the Externals kit, or it is a third party DLL (a
> "normal" DLL"). Revolution externals are loaded with the "set the externals
> to <list of externals>" command (see "externals" in the Transcript
> Dictionary), and third party DLLs *can* be used, but you have to provide an
> intermediary to call them (see the tip).
> Hope this helps,
> Ken Ray
> Sons of Thunder Software
> Web site: http://www.sonsothunder.com/
> Email: kray at sonsothunder.com
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution

More information about the use-livecode mailing list