Am 18.10.2017 um 02:36 schrieb Dwight: > For other users, a blank date translates to NOW, meaning get > on itor this will be overdue right away. I am in the first group > where blank-no deadline.
And I still think the second kind of usage with no due date = today makes little sense. The majority of my tasks is *not* due today - otherwise I would not need software, but could keep everything in my head. Also, in that case I wonder why there is a button "today" which sets the due date explicitly to today if it is empty. Yes, there would be another subtle difference with an empty due date and one of today in that tasks with empty due date would never be overdue, but I'm not sure if that is what you really want.
The situation is more controversial with "start date". The first meaning would be "the first day when the task theoretically can be tackled". For the most tasks this would be today, so the default would be "today" or "-infinity". In that meaning, it would only control whether the task is considered active or not, and should not influence the computed score very much. The second meaning would be "the first day when I *intend* to start working on the task, i.e. the start date would be used more like a "scheduled date". This makes a lot of sense, and I'm now using it that way since MLO lacks a dedicated scheduled date. In that meaning, the default (emtpy) value would be also "+infinity" (not scheduled yet), and it should influence the computed score very strongly.
My point is: Depending on which meaning you use, the software should also treat the fields differently, regarding empty values, default values, sorting, computed score, determining active tasks etc.
Currently the values are treated inconsistently in different places, which serves none of the groups very well.
So there should be a setting to elect one of these meanings, and the software should adapt the default values, sort order etc. according to the meaning the user wants to give to a field. Alternatively, the software could assume a fixed meaning, but then the documentation should explain exactly which meaning is anticipated, so that users don't give the fields a different meaning that doesn't harmonize with the meaning the software assumes and then wonder why they don't see what they expect in their lists.
-- Christoph -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/mylifeorganized. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/b6086d57-7b02-dc57-d19b-1b28dad0b874%40online.de. For more options, visit https://groups.google.com/d/optout.
