|
Post by Stefan on Jul 20, 2024 10:17:41 GMT -5
George,
Sorry, I'm in a macro-writing mood and just tripped over this. It's an issue with the official v3 release but not with v2 last beta v3.02.24091.
Scenario: You have IMACRO XXXX ON specified in the profile, and macro XXXX issues a HALT(FAIL,"some message") statement
In version v3.02.24091, regardless of a FAIL or OK return code, the message appears immediately after the file was loaded.
Any subsequent RELOAD command produces the same result.
In the current v3 Release version, regardless of the FAIL or OK return code, the message flashes up briefly but does not remain on the screen. Worse still, if you think "what was that I just missed?" and issue a RELOAD command, the macro goes into a loop usually resulting in SPFLite Termination. This loop does not occur if the HALT statement specifies OK or nothing.
This simple macro whould demonstrate - just set it as IMACRO for your test profile
000001 ' XXXX.Macro 000002 SPF_Debug("IMACRO-------------") 000003 ' Halt(FAIL,"Fail message - flashes up and RELOAD cmd results in loop/crash") 000004 Halt(OK,"OK message - flashes up but no loop when RELOAD is used")
|
|
|
Post by George on Jul 20, 2024 10:44:44 GMT -5
Stefan: OK corrected. A bit of history. When IMACRO was created, messages were simply not appearing, and it turned out a simple fix was to invoke internally a Do-After of an (Enter). Problem solved.
V3 has a new fix for messages issued by a macro which also created Do_After commands, the messages similarly 'blinked' and were gone. The fix here basically made the (Enter) of the first fix redundant (and much worse). The forced (Enter) commands have been deleted and it now seems fine.
I'll post a Beta for V3.
George
|
|
|
Post by Stefan on Jul 22, 2024 8:41:20 GMT -5
Hi George,
I confirm v3.1.24202 fixes this issue.
|
|