The mysterious CallDll object. Many of us klikers have tried to use it, but many times without results. In all honesty, CallDll can be more easily used in MMF than it can be in TGF. For those of you out there without a copy of MMF handy, I'd just like to lead you through some of the tricks envolved with working with 3EE's involved object.

Just to be straight forward, you'll be needing not only the CallDll object, but also the String Parser object. Why? I'll explain...

First off, this would be a command issued through a DLL in VB:

BASS_StreamCreateURL "http://www.xxxxxxx.com/radio/superap.mp3" , 0, 262144, "superap.mp3" )

If I were to type that into CallDll's Call Funcion dialogue within TGF, I'd get an error. Now, MMF has functions to simplify this on it's own. TGF, on the other hand, does not. For CallDll to recognise the commands, they must be in string form, and for TGF to recognise string forum, everything must be in quotations. That causes a problem:

"BASS_StreamCreateURL "http://www.xxxxxxx.com/radio/superap.mp3" , 0, 262144, "superap.mp3" )"

TGF will interpret an end string at the " preceeding that URL above. So what shall we do now? String Parser it up!

chr$( "String Parser", 34 ) is the same as a " sign, AND tgf can understand it when paired with our CallDll command:

"BASS_StreamCreateURL(" + chr$( "String Parser", 34 ) + "http://www.xxxxxxx.com/radio/superap.mp3" + chr$( "String Parser", 34 ) + ", 0, 262144, " + chr$( "String Parser", 34 ) + "superap.mp3" + chr$( "String Parser", 34 ) + ")"

Lemme explain what I just did... on the "'s that end the string command, replace " with chr$( "String Parser", 34 ). Adding the rest of the command bit by bit afterward. Although you are closing strings, CallDll interprets it as one whole command. Beats getting that annoying "Cannot Understand Your Expression" error. If you further need to know how to use CallDll, please consult 3EE or find a tutorial.