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.

Sign up for GitHub

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

Jump to bottom

Not possible to use 24h time format? #224

Closed
hapklaar opened this issue Apr 18, 2021 · 4 comments
Closed

Not possible to use 24h time format? #224

hapklaar opened this issue Apr 18, 2021 · 4 comments
Labels
status: markedForAutoClose Issue will be closed automatically type: enhancement New feature or request

Comments

@hapklaar
Copy link

The plugin only shows am/pm time format for me, I would like to have this in 24h notation.

image

In configuration I have this set this which should give me 24h format right?:

image
@OllisGit
Copy link
Owner

@hapklaar time format option for the current time will be in the next release.

@OllisGit OllisGit added status: inNextRelease Will be implemented/fixed in next release type: enhancement New feature or request labels May 10, 2021
OllisGit added a commit that referenced this issue Oct 14, 2021
@OllisGit
New Version 1.27.0
745b594 
- E #230 fire event when m600 occurs
- E #224, #182 adjustable current time format
- E #222 Option to disable "Layer indicator not found" popup
- E #221 Option to change "look ahead" line count
- B #213 filter empty lines from layer-expressions
- PR #234 typo, credit goes to @2231puppy
- PR #238 Added built-in support for Prusa layer counting, credit goes to @scyto

- reducing size of master.zip
@OllisGit OllisGit added status: waitingForTestFeedback and removed status: inNextRelease Will be implemented/fixed in next release labels Oct 14, 2021
@OllisGit
Copy link
Owner

Hi @hapklaar
the new release 1.27.0 with this feature is out now. It's now possible to adjust the date/time format.
E.g.
image
or
image

Please test and give feedback.

Thx, in advance
Olli

@OllisGit OllisGit mentioned this issue Oct 14, 2021
Closed
@stale
Copy link

stale bot commented Nov 14, 2021

This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.

@stale stale bot added the status: markedForAutoClose Issue will be closed automatically label Nov 14, 2021
@hapklaar
Copy link
Author

I haven't been able to test as I've since moved to Klipper + Fluidd. As soon as I have the chance I will though and report back if there are issues. Will close for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: markedForAutoClose Issue will be closed automatically type: enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hapklaar @OllisGit