Before Authorware can use a custom function, the function needs to be in memory. Loading a custom function is like opening an Authorware file: Authorware reads the function from the disk where it's stored into the computer's memory. Once the function is there, Authorware can exchange information with the function and tell it when to start. Loading a function connects Authorware with the function and allows the two to communicate. You can start the process of loading a custom function from the Functions dialog box, a Calculation window, or a text object. For more information, see Loading a DLL custom function in the Functions dialog box and Loading a DLL custom function in a Calculation window, dialog box field, or text object.
Authorware requires certain information about a custom function to be able to load it from a Windows DLL. Many existing custom functions contain this information in a form that Authorware can already use. For more information, see Return and argument types.
For information about loading Windows DLLs that don't contain the information Authorware needs, see Loading DLLs that don't follow Authorware conventions.
When a function is loaded, it takes up space in memory. If you're not using a function in the piece you're working on, you can remove it from memory and free up the space it occupies. For more information, see Unloading a DLL custom function.
Send me an e-mail when comments are added to this page | Comment Report
Current page: http://livedocs.adobe.com/authorware/7/using_aw_en/09_var41.htm