Tks for the tip Stirling.

At least no more wasting time.

So if i stick to button scripts, how do i get around the issue (or that it seems to be for me) that DoButton(3) stops the script execution so the instructions after that do not run?

Regards

GUYS it is working fine here ?  I just created a function based on the same thing you needed and used the same Macro code to stop and tested it.

What version are you running

(;-) TP

OK i have run it in Ver.042.022 AND .067 It works fine here.

(;-) TP

@Terry - It depends on what you mean by "it" and "working".

if you go back to your post Reply #7, then....

If there is currently NO movement in progress then...

if you execute your M1001 from a button, from the MDI, from the CB editor or from a trigger then it executes as you would expect i.e. IMMEDIATELY.

HOWEVER - If there IS currently movement in progress then...

if you execute your M1001 from a button, from the MDI, from the CB editor then again it executes as you would expect i.e. IMMEDIATELY.

HOWEVER IT DOES NOT EXECUTE IMMEDIATELY from a trigger - IT WAITS UNTIL MOVEMENT has stopped and THEN EXECUTES.

This is on 43.22 but I've tested it from 43.66 back to 42.18 and it's the same. Well it is here anyway - if a macro executes from a trigger immediately on your system WHILE movement is in progress then you have (AFAIK) the only system out there where triggers work FULLY and PROPERLY.

Ian