Skip to content
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

Use uptime instead of relative timestamps in console #113

Open
mfs12 opened this issue May 21, 2021 · 1 comment · May be fixed by #116
Open

Use uptime instead of relative timestamps in console #113

mfs12 opened this issue May 21, 2021 · 1 comment · May be fixed by #116

Comments

@mfs12
Copy link
Contributor

mfs12 commented May 21, 2021

To avoid a continuous updates and making the console log unsteady the uptime could be used as a timestamp of console messages. This would have several advantages:

  • nothing to update or calculate in the background
  • no visual updates in console screen except new message arrive, there for more steady screen
  • the added uptime in the top windows would provide interesting additional information to the user

Discussion:

  • Either use PanelDue Uptime or Reprap Uptime?

Idea:

  • Add uptime to top window frame
  • use uptime for console logs
@mfs12 mfs12 changed the title Use uptime instead of relative timestamps in Console Use uptime instead of relative timestamps in console May 21, 2021
@wilriker
Copy link
Contributor

IMHO uptime does not mean anything to the average user as they would have to remember when the machine was turned on. Especially for long-running industry-machines this can be impossible since they are operated by possibly multiple people and they would have to pass around the information of the last restart.

Either leave it at the current "so much time since this event happened" or get absolute time. But again for long running machines this means we have to also display date somehow and we only have limited screen estate.

While I see the advantages to switch to an another time base I think the current solution is as good as it gets.

If you insist on using uptime, my vote would be for RRF uptime.

@mfs12 mfs12 linked a pull request May 29, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants