issue has been identified, i believe, within FlexGUI, and an issue generated on that Git.
part of my problem was i was running incompatible operations. i was using MDI buttons to simulate auto operations. so i instead hand-wrote a crude Gcode program that selected a tool, started the spindle, did some moves with it. selected another tool, did some moves with that. and again, selected a third tool, and did some more moves. then stopped the spindle and ended program.
in case anybody is interested in how crude the code was:
github.com/travis-farmer/linuxcnc/blob/m...r/gcode/atc-test.ngc
image missing /media/kunena/emoticons/wink.png i don't suggest running it, unless you have the clearance to do so...
what i found, is that both Axis and FlexGUI ran the program flawlessly... that is to say it did exactly as coded, but not exactly as i wanted... image missing /media/kunena/emoticons/laughing.png
there was no hang of the GUI, so my theory that it has to do with the python c.wait_complete() hanging the code, is probably correct. but will it interfere with my normal operations? not if i do them as intended.
the real issue being that my routine took longer than the c.wait_complete() timout, and the GUI aborted the routine.
so long story longer, i made my recomendations to JT in the Git issue, based on my suspicions, research, and new tests.
