When gSender is in “Checking Gcode file” mode, the UI is locked even if you Stop the job
I have seen a few behaviors like this, where the UI gets stuck in a state, and the only way to clear it is to exit the program, and then re-launch.
I say this, because I dont believe this is the ONLY place it happens, but this is reproducible 100% of the time.
I have seen the following behavior when you Click START JOB, or TEST RUN.
Oddly, it only happens on the START JOB Randomly, but once it starts, it wont stop.
1 - Load the attached GCODE file
2 - Click on TEST RUN
3 - wait a few seconds, UI will update with a “Checking Gcode file” in the upper right of the screen
4 - Click on the Stop Job
5 - Note the Checking Gcode file doesnt go away.
6 - click START JOB
7 - Note that the confirmation still says Checking Gcode file (restarts at 0%)
8 - Click Stop Job
9 - Click Start Job
10 - Note that the confirmation still says “Checking Gcode” file (restarts at 0%)
The UI is stuck in this model till you let the “Checking Gcode” file hit 100%, otherwise its now stuck in this mode,
even if you click on RUN JOB, if its stuck in this state, it wants to complete the “Checking Code”, and only then will it stop
I want to be clear, I have this this “checking Gcode” when I click on the start button. but its usually after HOURS of running.
4-red-CLEARING.gcode (926.5 KB)
Video of the problem