Quote:I had a similar problem and am wondering whether the @macro command is set for a "default" directory.
When I went to install Sesame, I noticed that it defaulted to C:\Sesame
I preferred however to install it in C:\Program Files\Sesame
Sesame looks for macros, and much else, in the "current working directory". In Windows, that is set in the icon's properties and is called the "Start In" path. You can have a different CWD from the directory where the Sesame executables are installed.
Quote:When I used simply @macro("allrecords.mac") I had the same problem. If no macro was "loaded" - I got the "macro failed to load" message and the macro did NOT work. If the macro was "loaded", I got the "failed to load" message and the macro DID work.
Just wrote a new SBasic command that "unloads" a loaded macro. It will be in the next release.
Quote:When I used the full path @macro("C:\program files\sesame\data\allrecords.mac") it worked just fine. If I used the full path without the .mac extension I got the "failed to load" message.
The @macro command does want the file extension. You can name a macro file with any extension you want, so we cannot assume the .mac extension. If the macro file is in the CWD ("Start In" directory), you do not need the full path.
Quote:One additional question: Each time I open Sesame the "view" is for macro visibility "ON" Can I modify this so that it will ALWAYS open with a "view" of macro visibility OFF?"
When I read this, I thought - sure there is... but I checked, and there is no startup switch for this. I'll try to get it in the next release. I thought I put it in when I put in the "-blink" switch, but I guess I missed it.