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

Bug: task "overdue by" value skips a day #51

Closed
sir-pinecone opened this issue Mar 17, 2021 · 1 comment
Closed

Bug: task "overdue by" value skips a day #51

sir-pinecone opened this issue Mar 17, 2021 · 1 comment

Comments

@sir-pinecone
Copy link

I'm seeing the following behaviour when setting a deadline on a task:

Current day = 17th
Deadline = 16th -> Overdue by 1 day
Deadline = 15th -> Overdue by 2 days
Deadline = 14th -> Overdue by 2 days
Deadline = 13th -> Overdue by 3 days
...

This might be related to the timer issue I logged in #50.

@sir-pinecone sir-pinecone changed the title Task "overdue by" value skips a day Bug: task "overdue by" value skips a day Mar 17, 2021
SolarLune added a commit that referenced this issue Mar 25, 2021
FIX: Times shown on Timers no longer are truncated. This resolves issues where days that are shorter (for example, when daylight savings time kicks in) show as just 1 day, rather than 1 day, 23 hours.
Enabling Auto-save on projects that lack a project path now shows a message at the top-right in red text.
Adding auto-save clarification in settings menu and at top-right.
Adding prompt to ensure saving when a project has not been saved and auto-save is on.
INTERNAL FIX: Project sample rate is set after opening settings, so that the global audio sample rate can be properly loaded.
INTERNAL FIX: ioutil is deprecated; using os.CWriteFile instead, with 0666 as the permissions so that it creates the file with read and write permissions. Previously, this was writing the file without further writing permissions.
INTERNAL FIX: Double-clicking is made more consistent (relying on project.Time instead of time.Time{}, since lags due to autosave could take longer than anticipated) and easier (0.33 -> 0.5 seconds).
@SolarLune
Copy link
Owner

Hello, thank you very much for your bug report.

The last commit should've resolved this issue; both this one and the other one (#50) were caused by incorrect internal date handling around daylight savings time changes. Thanks a lot for the report, again!

Regards~

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants