The macro name doesn't support .. or . for directory names.
P.S. It doesn't raise FAILURE if the macro can't be found anyway. It raises SYNTAX.
The absolute best place for a macro DLL is in the same directory as the script which uses it, or a sub-directory off of where that script resides. That's where Reginald automatically assumes it is... if you don't specify a full path.
So for example:MACRO mymacros ... means "Load MyMacros.DLL which is in the same directory as this script".MACRO mydir/mymacros ... means "Load MyMacros.DLL which is in a sub-directoy named MyDir in the same directory as this script". (Actually, that appears to be what you're trying to do anyway with this "../" thing).
I don't support "../" in the macro name, but I do support a full directory path (starting with the drive name). If you use the full path, you can put the macro DLL anywhere. (But for scripts you distribute to others, avoid using full paths).
Probably the best policy for Reginald development is to have some sort of "Scripts" directory where you put all your scripts for development. When you make any Macro DLL, create a Project in that directory (and put the macro scripts in there of course). In any script that uses the Macro DLL, specify the Project dir name:MACRO projectdir1/macros1, projectdir2/macros2, projectdir3/macros3 |