-
-
Notifications
You must be signed in to change notification settings - Fork 19.3k
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
Baby-stepping show millimeters on LCD #4028
Conversation
} | ||
if (lcdDrawUpdate) lcd_implementation_drawedit(msg, itostr3sign(babysteps_done)); | ||
if (lcdDrawUpdate) lcd_implementation_drawedit(msg, ftostr43sign(distance_done)); | ||
if (LCD_CLICKED) lcd_goto_previous_menu(true); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you don't need babysteps_done
any more - drop it everywhere.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I kept it in the latest update to get rid of some irritating rounding error from incrementing a float.
} | ||
if (lcdDrawUpdate) lcd_implementation_drawedit(msg, itostr3sign(babysteps_done)); | ||
if (lcdDrawUpdate) lcd_implementation_drawedit(msg, ftostr43sign(distance_done)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you do this here instead…
if (lcdDrawUpdate)
lcd_implementation_drawedit(msg, ftostr43sign(
0.001f * ((1000 * babysteps_done) / planner.axis_steps_per_mm[axis])
));
…then you don't need to define distance_done
above, or set it to 0.0
below. And this won't be called except when the value changes, so it doesn't cost any extra CPU.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is certainly simpler than carrying distance_done around all over the code.
Right now, I'm working directly with my cloned repository at github. Once I've figured out how to connect that up with my Mac, I'll have a command-line (and a decent editor) to work with.
To squash commits is pretty straightforward from the command-line. |
OK. I thing I got the commits squashed together on my end - but it looks chaotic over here for such a simple fix... |
If you have squashed your commits, please use |
Do I have access to the command line on my github account? That's where I've been making the pull requests via the web. Or do I need to bypass that and somehow push to the Marlin account from my Mac? Sent from my iPad
|
@edwilliams16 ... I know the feeling... I am not a mac owner, but this URL does shows all the bits and pieces I Then you'll get help from the community to fill the gap...(gaps :-) ) 2016-06-15 6:48 GMT+02:00 edwilliams16 [email protected]:
|
Make LCD show mm displacement on LCD not steps
Reduce FLOP count and improve rounding. Reset initial distance done when changing axes.
Got rid of redundant distance_gone
I added some scripts to help working with Marlin and git from the command-line. They live in
To master git you should go through this interactive tutorial: http://learngitbranching.js.org/ |
Here is how I'm cleaning up this PR…
Opens up an editor, where I edit it to say:
I save this, the editor reopens so the "reword" commit can be edited.
And the browser opens up, ready for me to create a PR. |
@edwilliams16 It is quite easy:
|
Merge duplicate strings in cmdqueue.cpp
Change babystepping so that mm not steps are displayed on the LCD.