-
-
Notifications
You must be signed in to change notification settings - Fork 305
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow sending blank lines from the MDI (Terminal). #364
Comments
what is a blank line ? because webui send : Let me know what should work and I wil add it - I also can add a variable if necessary to replace any not printable char |
|
Not without further code changes to the backend. I prefer |
I have modified the webui to allow nothing as test but I forgot it add automaticaly a timestamp to bypass the cache : |
Timestamp is ok and I guess needed when there is a proxy in between. |
Can you give a try to : |
Works! Thanks for quick implementation. |
Ok I will push it - I have just changed one thing compare to the version you test : emptyline won't go to history of command because it is not easy to see what command is that |
Implemented in version 39 d723801 |
@terjeio you are welcome , it was an easy fix and happy it is useful ^_^ |
Again thanks, I'll report the fix in the OpenBuilds thread when I have pushed the change on my end. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Is your feature request related to a problem? Please describe.
grblHAL repeats the last error until cleared by a blank line or a $-command for safety reasons. The v3 WebUI does not allow sending blank lines from the MDI.
Describe the solution you'd like
Allow sending blank lines.
Describe alternatives you've considered
Setting grblHAL compatibility level > 0 disables this safety feature alongside some other new features supported by the WebUI - tool changes is at least one prominent one. IMO not a good solution.
Additional context
See this OpenBuilds comment onwards.
The text was updated successfully, but these errors were encountered: