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
[Request] API should allow pause and unpause, not just pause-toggle #1393
Comments
Hi @MarcusWolschon, It looks like there is some information missing from your bug report that will be needed in order to solve the problem. Please take a look at the Contribution Guidelines which will provide you with a template to fill out here so that your bug report is ready to be investigated (I promise I'll go away then too!). If you did not intend to report a bug, please take special note of the title format to use as described in the Contribution Guidelines. I'm marking this one now as needing some more information. Please understand that if you do not provide that information within the next two weeks (until 2016-07-14 05:10) I'll close this ticket so it doesn't clutter the bug tracker. This is nothing personal, so please just be considerate and help the maintainers solve this problem quickly by following the guidelines linked above. Remember, the less time the devs have to spend running after information on tickets, the more time they have to actually solve problems and add awesome new features. Thank you! Best regards, PS: I'm just an automated script, not a human being, so don't expect any replies from me :) Your ticket is read by humans too, I'm just not one of them. |
Relevant code: Documentation to update: Js code only needs to be updated if the user interface would make use of it, does it? |
Implemented in Simply changing the behaviour of the |
Version 1.2.13 (master branch)
The API
http://docs.octoprint.org/en/master/api/job.html#issue-a-job-command
allows for a "command": "paus" described as:
"Pauses/unpauses the current print job."
Issue:
Issuing a pause command twice for any reason (timeout, response not parsed properly, script was restarted,..) resumes the print instead of keeping it paused.
In my case I'm using the pause command for a Filament monitor.
http://marcuswolschon.blogspot.de/2016/06/ultimaker-ii-filament-sensor-and-remote.html
Obviously having any chance of accidentally resuming a print instead of pausing it, is dangerous.
Proposal:
The current command is nice for user interfaces used exclusively by humans.
For automatic scripts it should offer 2 command to
pause and to resume a print regardless of state.
The text was updated successfully, but these errors were encountered: