by MRob » Thu Dec 12, 2019 6:11 pm
Oh! Lol OK I think I have you now.... so, let me rephrase the answer, see if I have it correct?
- UCCNC does not stop macros when "cycle stop" is pressed, this is by design - if you want this behaviour, you have to modify any user created macros you are making, to include the code you have given me, each time an axis is being told to move, after the "while(exec.IsMoving());" line. This is because pressing cycle stop will end the current action, but UCCNC will then move onto the next. But with this code, instead before moving to the next action, it sees the correct Ismacrostopped condition, and kills the entire macro.
Have I got that correct? I didnt understand the code was supposed to go into each macro I was making, thought there was some other place it would have to go..
Hey one more question - a quick and easy one I promise.. I tried exec.AddStatusmessage(variablename); to try and display variables from the macro, like the doubles I was writing in, but it didnt work. Also tried a line like string stringname = variablename as string; as shown in the macro manual, and a few other combinations, but it didnt like that either. Is there any way to make this happen? It would be really useful to be able to display the value of variables in the status bar, partly for any future debugging I might have to do, but also it would be nice to check how consistent the home switch compared to probing locations are.