Looking in my task file, some tasks have a due date of 2012-05-26 23:59:00, others have 2012-06-24 23:59:59.999999. When I sort tasks by Subject and then Due Date the results don't appear to have a secondary sort of Subject.
When I created a new task just now the due date was 2012-06-24 23:59:59.999999. My default due date is "today" "end of day". I can make the task recurring, complete an instance and have the task rescheduled, and the fractional seconds remain.
However, if I change the due date by going to the Dates tab and changing the due date widget (not touching the time widget) the time is changed to "23:59:00" -- presumably just reading from the time widget and writing the value.
This behavior wasn't obvious until I experimented as I don't remember which recurring tasks I previously changed the due data on.
An easy solution to this issue would be to change the "end of day" time to "23:59:00" and have Task Coach clear seconds on save. (Clearing on load would produce a modified file before the user did anything.) However I have no idea if that change would have negative consequences somewhere else.
Another solution would be to have an explicit "end of day" option in the time setter, but that would clutter up the UI (and I don't see a significant advantage to the feature) and it wouldn't clear up the problem in existing task files.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I really like your idea of including "end of day" in the time dropdown menu. We'll see what the others on the development team think. Thank you, by the way, for being so clear and for testing things. We really appreciate it!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
BJ, As you may know, we've completely replaced the date/time system. You can now use E and S keys to instantly jump to start and end of day and shift as a modifier for work-day. So none of the bugs with the old system matter anymore. Closing this.
Cheers
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No, the issue isn't fixed. I just created two tasks with 1.3.23. The first I didn't touch the date page and the due date ends in 23:59:59.999999. The other I changed the due date and the due date ends in 23:59:00. Set them recurring, and the date is moved forward with the minutes unchanged.
I end up with both types of tasks in my task file. This means that when I sort by subject and then by due date (so subject should be the secondary sort) the events for each day are not alphabetical because of the two types of due dates.
Attached is a task file with the two tasks (before the recurrence was set).
And the platform isn't Windows, I created those two tasks on Ubuntu.
Ok, I misunderstood. The problem is that 23:59:59.999999 is used as "end of day" when set in the proposed or preset times in the preferences then? So the point is just that this is a funny and otherwise incompatible time and should instead be just 23:59. At any rate, whatever we use for "end of day" should be compatible and predictable and normal.
Anyway, there is indeed now an "end of day" shortcut by type "E" while editing time. So that's set and should be consistent.
But we'll have to make sure the time used for that, both in preferences and in this shortcut, makes sense and won't interfere with anything if it is later changed or recurs.
Opening the ticket again, thanks for clarifying
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We use 23:59:59:999999 because a user will less probably choose this value than 23:59:00 :) I'll try to fix the date picker, and fix such date/times on the fly when reading an old task file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A fix was made and checked into the source code repository of Task Coach. The fix will be part of the next release. You will get another notification when that release is available with the request to install the new release and confirm that your issue has indeed been fixed.
Because a fix has been made for this bug report, the priority of this report has been lowered to 1 and its resolution has been set to 'Fixed'.
Thanks, Task Coach development team
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This bug should be fixed in the latest release of Task Coach. Can you please install the latest release of Task Coach and confirm that this bug has indeed been fixed?
Thanks, Task Coach development team
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's a crazy time. Definitely a bug.
I'm guessing this had to do with how time got entered maybe, and it might be connected to this other bug:
https://sourceforge.net/tracker/?func=detail&aid=3554613&group_id=130831&atid=719134
Not sure about that though.
When I created a new task just now the due date was 2012-06-24 23:59:59.999999. My default due date is "today" "end of day". I can make the task recurring, complete an instance and have the task rescheduled, and the fractional seconds remain.
However, if I change the due date by going to the Dates tab and changing the due date widget (not touching the time widget) the time is changed to "23:59:00" -- presumably just reading from the time widget and writing the value.
This behavior wasn't obvious until I experimented as I don't remember which recurring tasks I previously changed the due data on.
An easy solution to this issue would be to change the "end of day" time to "23:59:00" and have Task Coach clear seconds on save. (Clearing on load would produce a modified file before the user did anything.) However I have no idea if that change would have negative consequences somewhere else.
Another solution would be to have an explicit "end of day" option in the time setter, but that would clutter up the UI (and I don't see a significant advantage to the feature) and it wouldn't clear up the problem in existing task files.
I really like your idea of including "end of day" in the time dropdown menu. We'll see what the others on the development team think. Thank you, by the way, for being so clear and for testing things. We really appreciate it!
BJ, As you may know, we've completely replaced the date/time system. You can now use E and S keys to instantly jump to start and end of day and shift as a modifier for work-day. So none of the bugs with the old system matter anymore. Closing this.
Cheers
No, the issue isn't fixed. I just created two tasks with 1.3.23. The first I didn't touch the date page and the due date ends in 23:59:59.999999. The other I changed the due date and the due date ends in 23:59:00. Set them recurring, and the date is moved forward with the minutes unchanged.
I end up with both types of tasks in my task file. This means that when I sort by subject and then by due date (so subject should be the secondary sort) the events for each day are not alphabetical because of the two types of due dates.
Attached is a task file with the two tasks (before the recurrence was set).
And the platform isn't Windows, I created those two tasks on Ubuntu.
Ok, I misunderstood. The problem is that 23:59:59.999999 is used as "end of day" when set in the proposed or preset times in the preferences then? So the point is just that this is a funny and otherwise incompatible time and should instead be just 23:59. At any rate, whatever we use for "end of day" should be compatible and predictable and normal.
Anyway, there is indeed now an "end of day" shortcut by type "E" while editing time. So that's set and should be consistent.
But we'll have to make sure the time used for that, both in preferences and in this shortcut, makes sense and won't interfere with anything if it is later changed or recurs.
Opening the ticket again, thanks for clarifying
We use 23:59:59:999999 because a user will less probably choose this value than 23:59:00 :) I'll try to fix the date picker, and fix such date/times on the fly when reading an old task file.
A fix was made and checked into the source code repository of Task Coach. The fix will be part of the next release. You will get another notification when that release is available with the request to install the new release and confirm that your issue has indeed been fixed.
If you like, you can download a recent build from http://www.fraca7.net/TaskCoach-packages/latest_bugfixes.py to test the fix.
Because a fix has been made for this bug report, the priority of this report has been lowered to 1 and its resolution has been set to 'Fixed'.
Thanks, Task Coach development team
This bug should be fixed in the latest release of Task Coach. Can you please install the latest release of Task Coach and confirm that this bug has indeed been fixed?
Thanks, Task Coach development team
Yes, the problem is fixed--I can now show my tasks alphabetical bu due date, and they are easier to scan.
Thank you.
Thanks for reporting back.