Upgraded from 6.6 to 6.6.1 (Portableapp environment).
Launched ToDoList, both my tasklists were auto-loaded as usual. However, tasklist 2 has one overdue task, and thus its tab has a red triangle. This disappeared in 6.6.1.
Switching lists and playing with preferences brought no luck.
Finally, shutting down TDL and re-launching it twice seems to have fixed the issue, but I will keep an eye out if it crops up again.
Edit 1: Launched it again after midnight with tasklist 1 in focus. Now tasklist 1 has tasks due today, so its tab gets a purple triangle. However, tasklist 2 with its overdue task lost its red triangle again.
Re-launched TDL; now both purple and red triangles respectively are visible.
Edit 2: TDL 6.6 beta 5 on another drive exhibits the same behaviour — i.e., tasklist 2's tab has no red triangle despite the overdue task.
It looks like TDL is incorrectly determining the 'Earliest Due Date' under some conditions. TDL writes this value into the tasklist so that it doesn't have to load the entire tasklist to find out if it has some due tasks.
I'm looking for a way to get a notice that when I've overcommitted myself - e.g. according to my estimates I'm already globally committed for 42 hours over say the next 120 hours (5 days), but I've only set aside 40 hours for work during the same period. I guess this requires a query of some sort that takes into account 1) the time estimate; 2) the work day; and 3) the due date of all the tasks in a list. Any idea how to get this info out of TDL? The idea is that, before the pressure gets too intense, I will be able to either postpone some due dates, renegotiate my commitments, figure out how to eat and sleep less, etc.
Unsure how exactly you deal with your tasks, but assuming each task has an estimated duration and will be dealt with in the time period you specify...
I would go to Listview, and then filter for the tasks you are interested in reviewing (hiding parents) - tasks that are to be completed in a given time period, tasks to be done in a work day (if you have non-work tasks in there as well), etc, etc. You can set up a customer filter through the "Find Tasks" function.
You could then either sum up the estimated hours visually in the grid, or run the stylesheet Z_TimeSpentReport.xsl (via print preview). You would still need to sum up the estimated times though.
For something a bit better looking (with some summated time estimates), you could apply the same filter to the tree view, and then run the stylesheet. For a focus on just the tasks, and not the parents, you could modify the stylesheet (using a text editor) as follows:
<xsl:param name="showOnlyLeaves" select="0" />
<xsl:param name="showOnlyLeaves" select="1" />
Either way, this is a somewhat manual process, and doesn't automatically alert you.
PS: "showOnlyLeaves" defaults to showing the task path. I was going to make this an option, but forgot. You can get it to not show the tasks path by commenting out the code below under section 46:
<xsl:if test="$showOnlyLeaves=1"><!--Need to see the task ancestors-->
<xsl:text> [Path: </xsl:text>
Neither of the two custom columns that I created in TDL 6.6 beta appear in the Column Selection dialog. Both columns are listed in the Add Custom Task Attribute to Tasklist dialog, though, so they still exist.
It looks like a bug that I reported earlier made it back into TDL. I like to color tasks by category, but in this release I can't add any to the "Colour task titles by" option. Also, if I select a different radio button for the color choices, the radio button for "Colour task titles by" is disabled and I can't select it again.
This happens to me on Win 7 when I go to System Properties, select the Advanced tab, click Settings in the Performance section, select the Custom radio button in the Performance Options dialog, unselect the check box "Use visual styles on windows and buttons," click OK twice, then close and reopen TDL.
If you select that check box again and then restart TDL, the red check boxes will be gone.
Thanks for your continuing work on this. Previous to this version, a recurrence that creates a new task would cause the new task to copy the custom attribute values from the old one. That doesn't seem to happen anymore, at least by default. Is there an option now somewhere to re-enable this behavior?