Fixes problems in autoleveler with scaling between metric and imperial units #2273
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… of the probed values
… the units from the positions instead of and explicit one.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Removed the setting for switching between imperial and metric, instead use the global setting for preferred units.
To better see the probing difference, the low/high color is now based on the differences between the highest/lowest probed points instead of the min/max settings. This will improve the visualization of smaller differences of a probed area.
Fixed scaling bug so that probe data in imperial/metric on gcode expressed in either imperial or metric. It will now also scale feed rates properly.