Good morning/evening!
I have been experiencing a weird behavior with variables in ngcgui routines and I couldn’t find any topic with similar issues in forum.
Whenever I happen to stop a program before its natural end, every variable that I might set will assume the value as if the program had ran until the very end!
I believe this is not an expected behavior. I don’t know if it is a bug or not, but it looks like one. I have attached configuration files with a sample able to reproduce the issue.
To use it, please, go to the only ngcgui tab available (so called “macro”), create a feature and then finalize it. Proceed to run the program. The only thing it does is decrement the variable #1000 by 1 every time it loops. (The variable #1000 has been added to linuxcnc.var and its starting value will be =1000)
If one let the program run until the end the variable #1000 will end up =900.However, if you stop the program mid execution, it will also end up =900! Even if you stop it in some other value, like 998. No matter how long the program runs, it will end up 100 units less than it started.
For test conveniency the program will print variables states in every loop. There are two auxiliary pyvcp buttons as well. One to show variables states (useful for immediately after one aborts the program) and another one for restoring the value of variable #1000 back to 1000.
I hope this will help solving this issue.
Thank you all in advance!
Bruno
