Hi Peter,
(I’ll assume you meant BitSetter throughout, not BitRunner? )
This has indeed been discussed a few times, and the bottom line is:
- this was deemed by the development team the best solution to cover a number of usecases to make the process user-proof.
- it is quite debatable, it has been debated (a lot), and to this day the final word from the boss is this.
So for now, should you want an alternative workflow, you would have to use a different G-code sender (don’t tell anyone, but I secretly use either CM or CNCjs with @neilferreri’s probing macros for my BitSetter)