Accuterm "Edit Macros..." disabled on startup.

[Joe G]

A strange thing just happened to me in AccuTerm 7.1a.  I use macros to set up my workspace for various tasks. I go to Tools->Macro->Edit Macros... to load up the main script and then run the subroutine that loads the sessions and arranges them the way I want.

For some strange reason, the "Run Macro" and "Edit Macros..." menu items are disabled. If I go into the script editor it shows the "Main Script" as blank.  If I record a macro and save it, everything starts working.  The run and edit macro menu items are enabled.  If I select "Edit Macros..." it goes into the script editor and the title says "AccuTerm Main Script [AccuTerm Macros.atsc]"  All my login scripts are there but they're in a "script" tab and not in the "Main Script" tab.

 The "Main Script" tab is an empty macro, just Sub Main() and End Sub.

I've tried rebooting and even re-installing AccuTerm to no effect.  I think it's gotten confused as to where the script is located. I've looked through all the settings and even searched for .ini files but was unable to find anything.

Any ideas?

[Pete Schellenbach]

Hi Joe - this is very strange behavior you are seeing. The only thing that I can see that might cause this sort of behavior is if the macro file (AccuTerm Macros.atsc) is somehow slightly corrupted. There is a simple parser that scans the macro file for lines that begin with "SUB" and contain special comments that begin with '<MACRO, '<SHORTCUT or '<DESC. If for some reason these comments are mangled or the SUB line is not found, then the module would not appear to contain macros, and those menu items would be disabled.

Thanks, Pete

[Joe G]

That was it.  I had removed the comments.  I added them to the top but that didn't do it.  I put this at the top of the file;

Sub test
    '<Macro = Macro1>
    '<Desc = recorded 6/29/2017 1:31:54 PM>
    On Error Resume Next
End Sub

And that fixed it.  I guess you have to have the comments inside of a sub.

I had made a lot of changes and didn't know which one had caused the issue or if something else was going on with my system. I didn't even think that removing comments would affect anything.

Do  you need to scan for macros in an .atsc file? It seems like it would be safe to assume it's a macro file based on that alone. If it's not a macro then the interpreter will tell you that. Maybe at the time you were trying to accept files regardless of the extension but I think the file extension could safely take priority over any other scanning in most scenarios. Maybe a non-macro could cause issues if you load it so you need to check it first? Could that somehow stop AccuTerm from running?

Everything is working normally now.  Thanks for the help!