-
Notifications
You must be signed in to change notification settings - Fork 412
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
[Suggestion] 24h notation #99
Comments
Sorry, I am having trouble understanding you. The Cronicle logs are already in 24 hour notation, localized to whatever your server's timezone is. Example:
Can you elaborate on what you mean specifically, and provide an example log? |
Ah, thank you. Understood. I'll add this to the TODO list, and make it configurable per user. Thanks! |
It will be implemented in Cronicle v2 (Orchestra), which will be released this year (2023). |
Any news on this, and the v2? |
@robfordww I'm so sorry for the long delay. I am working on Orchestra every day, and it is coming along nicely, but it is just taking way longer than I anticipated. Life keeps getting in the way. New estimate is early 2025. Deepest apologies for my incorrect prediction. |
Thank you for your prompt feedback. I completely understand how life can get in the way sometimes. I'm excited to see version 2 whenever it’s ready, and I’m hoping it includes more internationalization options, like support for the 24-hour clock for those of us who prefer it. 😊 |
Summary
We are having some issues with 0:00 AM / 0:00 PM / 12:00 AM / 12:00 PM when creating a new event and when reading logs, I sometimes mix up night and day for some reason.
A 24h notation could be very useful.
Thank you in advance !
Cronicle software version?
Version 0.8.23
The text was updated successfully, but these errors were encountered: