-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
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
Take apart kill() #2126
Take apart kill() #2126
Conversation
in kill() and kill_() to separate the message on the display. kill() will display MSG_KILLED on the display as before and call kill_(). kill_() has all the functionality of the former kill() but the message on the display. This change gives the possibility to use kill_() with a reason for the kill without overwriting it by MSG_KILLED. The output on the serial is not changed.
Pretty sure you can come up with better function names then "kill_" |
kill_without_display_massage() ? |
kill_quiet |
kill_quiet |
OK. kill_quiet_LCD ? it is longer... but clearer? |
sorry, to ask, but why should we have more than one kill? Bernhard On Wed, May 20, 2015 at 3:58 PM, CONSULitAS notifications@github.com
|
@bkubicek We call kill() for: kill button, M112, max_inactive_time - here MSG_ERR_KILLED is OK. |
I could use a parameter for the message - but than we'll have MSG_ERR_KILLED at least 3 times in memory. |
Identical PSTR() strings are pooled and combined into memory. |
How about a c++ variant?
Here at least kill_quiet_LCD() is not public |
Replaced by #2130. |
in kill() and kill_()
to separate the message on the display.
kill() will display MSG_KILLED on the display as before and call kill_().
kill_() has all the functionality of the former kill() but the message on the display.
This change gives the possibility to use kill_() with a reason for the kill without overwriting it by MSG_KILLED.
The output on the serial is not changed.