I like this program very much, but very often, when I mark a subtask ask being complete, all the tasks above it disappear from the screen! Then I have to do a collapse-all and expand-all to get everything back on the screen. Another way to get everything back on the screen is to use the up arrow. Is there any way to not have that stuff disappear? Thanks!
An active filter might explain that the "tasks above it disappear from the screen" and that they reappear when Member 9172785 uses the arrow up key.
There where several posts in the last months that dealt with little problems with the view and the necessity of the use of the arrow key to solve that. I can't recall them all but I think this little problem started with the filter option w) and showed up in different situations.
It probably does not happen when there is no filter, but I usually use at least one filter due to having a large number of tasks. It is happening right now when I show "Tasks Due by Today" and have 5 things checked under the Status filter, but that is not the only filter combination where this happens. While testing, I just noticed that UNDO (Ctrl+Z) can also make this same thing happen, and upon further examination, it's not only the tasks above the one I'm checking off that disappear, but some below too! I will try to examine what is happening more carefully as I use ToDoList to see if I can identify any more clues or patterns when this happens. One more thing (if it matters) is that I have some top-level tasks like "Daily Tasks", "Weekly Tasks", etc. that contain my actual tasks, so all of the tasks that I check off are actually sub-tasks of these
It IS fixed (in the 6.6DR version)! Tasks are no longer disappearing when I mark a task as complete. They are also NO LONGER disapearing when I do undo or change filter settings. This is MUCH better. Thanks for the quick fix for this issue! -Steve-
Could we have a little more control over the modified date field? I often find that owing to my poor typing skills I have to edit tasks in order to correct typing errors. This is recorded in the modified date field, but for me such actions are not significant modifications meriting recording in this way.
So, would it be possible to allow the user some leeway in changing the modified date field for any edits?
First: Thanks for the great Author Dan. i just downloaded yesterday this wonderful program, and It's amazing how outstanding and superior this program is, much much more than many other "costly" programs that i tried in the last few months. simple and neat, flexible, beautiful and perfect design, great features to the need, excellent functions, and it seems to go forward with much more.
one of the suggestions that i have for the next update of this program, that in the preferences at the settings for colors based on 'due date' 'category' 'completed task' and others, should also have all other formatting options to chose for each criteria, as font, font size, bold, underline ETC. this will b great when someone wants to define different formatting for a few conditions of tasks in the task list at once.
I ran the test on my Gateway DX-4320 (AMD with 4 CPUs and 6GB ram) and it took 32 seconds under Windows 8 with TDL 6.5.10.
I ran the same PC using Remote Desktop Connection from my iMac and it took about 2Min. and 15 sec.
Also, I Ran the test under Parallels on my iMac running Windows 7 with TDL 6.5.10 and it took about 2Min and 17 sec. My iMac is a 2011 model with I5 processor and 8GB ram with 4GB dedicated to Parallels.
Old laptop - Intel Pentium M 1600Hz, 1.5GB RAM running Win XP SP3
TDL 6.5.5: 25 sec and 1m12sec
TDL 6.5.10: 25 sec and 1m12sec
TDL 6.6d2: 30 sec and 1m11sec
Where the first value is the TDL window at ~a quarter of the screen and the second value is with the TDL window maximised. In both options the CPU gets close to maximum when the arrow down key is pushed down. When the key isn't depressed, the CPU is at about 4%.
For what it worth, the screen is 1680x1050.
[EDIT] Work laptop Lattitude E5420 x86 Family 6 - 2500MHz, 4MB RAM, WinXP SP3, 1366 x 768 screen
TDL 6.1: 23 sec and 36 sec
TDL 6.5.5 26 sec and 36 sec
Again where the first number is when the TDL window is ~ 1/4 of the screen, and the second number when it is maximised. CPU runs at ~30% when scrolling.
modified 17-Nov-12 3:20am.
Last Visit: 31-Dec-99 19:00 Last Update: 22-Nov-14 23:58