Two bugs: saving and delays executions

[guli34]

When I do control S in editor the saved modifications are not always reflected right away I have to quit ME and restart to see the change ex add an item in a text menu

The other bug

I just noticed is the delays in variables are not completely applied, when you call a macro thru a run macro

In that case the macro goes too fast but if you call the same macro by itself I’m getting the results expected

[guli34]

I just found the reply from Kevin about the variable in an other post but still not sure about the save issue

 

"Each variable is cleared when a macro runs. The only exception to this is if one macro calls another via the Macro Run command. In that case all variable values are passed to the called macro. "

[rberq]

On the speed issue: does your calling macro set a playback-speed factor? I can reproduce your complaint only by:

(1) Setting playback speed of, say, 10X faster than normal in the calling (first) macro,

AND

(2) Unchecking the ignore-speed-factor box in the delay commands of the called (second) macro.

When run stand-alone, the second macro has no speed factor in effect, so timings are just as coded. When called, the second macro runs according to the speed factor set in the caller.

 

Make sure that "ignore speed factor" is checkmarked in all the delay commands, and see if that fixes it.

[guli34]

On the speed issue: does your calling macro set a playback-speed factor? I can reproduce your complaint only by:

(1) Setting playback speed of, say, 10X faster than normal in the calling (first) macro,

AND

(2) Unchecking the ignore-speed-factor box in the delay commands of the called (second) macro.

When run stand-alone, the second macro has no speed factor in effect, so timings are just as coded. When called, the second macro runs according to the speed factor set in the caller.

 

Make sure that "ignore speed factor" is checkmarked in all the delay commands, and see if that fixes it.

 

Well I think you got it it was exactly the issue do you have any idea about the saving problem in editor?

[rberq]

do you have any idea about the saving problem in editor?

The only similar thing I have seen is, if I edit a timer-scheduled macro, and save it at the same time it happens to run, I'll get a message about the macro file being invalid, and the editor will abend. But when I start the editor again, my changes have been saved properly.

 

I have seen a timing oddity in the editor itself. If I use Alt-d to dup a command, then immediately hit the Enter key to edit the new statement, sometimes it will pop up as a raw statement as if I had selected it from the command list on the left. For example, if the statement I duped was VARIABLE SET INTEGER N44 TO 17, it will pop up as VARIABLE SET INTEGER N1 TO 10 -- the same defaults as if I had inserted it via the command list. If I simply select Enter or Cancel to close the editing panel, then edit the statement again, it is fine.

 

So it's sort of a timing issue like what you are seeing, but probably unrelated because in my case the time delay is very short. Both cases are very minor irritations, makes the day more interesting.