Fix for handling temperature G-code commands with float values #14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do and why is it necessary?
In my configuration, Cura is generating temperature setting G-code lines with float values like this:
M140 S50.0
Those work fine with Octoprint and Klipper, but seem to cause issues with SmartPreheat:
Removing the fraction part from the G-code file fixes the issue, but I think SmartPreheat should also be able to handle them as well.
How was it tested? How can it be tested by the reviewer?
I've used it for several prints in my x86 Ubuntu/Python 2 based Octoprint+Klipper setup.
To test, modify a G-code file and add the fraction part to M104/M140/M109/M190 commands.