When I search for a word it highlights the task heading where the word is but it doesn't highligh the word if it is in the comments section. A very uuseful feature would be if all of the search words was highlighted no matter what section they were in.
When you log on to Code Project ToDoList page it highlights any new item in yellow. This would really work well if all of the search words were highlighted in yellow.
I think it is already possible to do what you want with custom filters (CTRL + F)...
By using relative start date and due date criteria, you can create some filters in order to only display active tasks (so hide not active tasks)
In yout system, how do you take over your task, if you want to do some modification, before the targeted date ?
In my opinion, it is better to see by default all tasks, then you filter, depending on your needs.
Personnally, I have several custom filters :
* DUE TASKS
* ACTIVE TASKS (including DUE TASKS)
* ACTIVE TASKS + TASKS STARTING or FINISHING within the next 7 days
* NOT STARTED TASKS
And keep in mind that custom filters can be saved and easily used (in the combobox 'Show'), so it is very easy to use.
But it is just my point of view, each person have its own way of working
This has come up before, ages ago. I am wondering about the behaviour of TDL when completing tasks in List view.
I have a filtered and sorted list of tasks in List view. I am going through this longish list, adjusting attributes and completing items. I change:
- % complete, name etc - the fields update - no issue
- Custom flag (a sorting item) - no immediate re-sorting - no issue
- Due date (a sorting item) - the task moves - not ideal, but OK
- Completed (tick) - the task disappears. Sometimes focus is lost, sometimes focus is given to another task miles away from where I was working - annoying.
My question: Would it make sense for no re-sorting action to take place until you select another task? In other words, you do all your editing on task A, select Task B, at which point Task A moves to wherever it needs to go. This would allow an orderly progression through the list, without unnecessary scrolling IMHO.
Would it make sense for no re-sorting action to take place until you select another task?
I'm not keen on this because it divorces the action from the consequences, which I believe would create a sort of disjointedness in how people understand the software to behave.
My ideal would be to restore the old preference to not resort on edit changes and to rely on the user refreshing the sort order when they are ready to do so. Not perfect because it pushes it back on the user but at least consistent from a behavioural perspective.
Completed (tick) - the task disappears. Sometimes focus is lost, sometimes focus is given to another task miles away from where I was working - annoying.
I hear you and will spend some time in 6.7 improving this. Sometimes it's tricky though if the completion is the last of a group of subtasks and it causes the parent to become completed and then further up the parent chain. Tricky but not impossible.
Custom flag (a sorting item) - no immediate re-sorting - no issue
Thanks for considering Dan.
I agree that having a preference to switch off auto re-sorting would be useful.
For me ideally when completing a task, if it disappears, I would like the one above or below to be selected (when in list view).
This should cause a resort.
I will check again later sometime. I ended up having to reboot last night as the laptop was doing some odd things, and this may have been affected.
When printing a report from a stylesheet in 6.7 (e.g. Z_DetailedReport.xsl), it seems the 'assigned to' no longer appears in the report. Priority, % done, name, start and due dates seem fine.
Printing the same file, using the same stylesheet from 6.6.3 works as expected.
You may not recall but I mentioned that I was going to 'fix' the way categories, tags, alloc_to and dependencies were stored in the task list.
Now that you mention it...
And I did notice the number value in the TDL file (but didn't spot any multiple entries to trigger my memory).
And I was going to update my code to handle this.
Sorry for the false alarm.
After much mucking around, this turns out to be really easy.
The @ signifies an attribute, which category no longer is. Therefore to make the above code work, replace "(@CATEGORY)" with "CATEGORY". Job done.
FYI. Previously, when adding several attributes, you would have @CATEGORY1, @CATEGORY2 etc... Now you access multiple nodes using CATEGORY, CATEGORY etc...
Entering file:///c:\sandbox\something.txt works when entered in the comments pane of a task.
However entering file:///c:\documents and settings\users\sandbox\somethingelse.txt does not work.
It breaks at the first space encounted in the path or filename.
Have not found any way to fix this, even with quotes at various places.
For now, I have been using the DOS short filename, which is not every descriptive.
Any ideas somebody?
Sometimes, when importing tasks in outline (.txt) format from windows clipboard, tasks appear to be long or excessive and need editing prior to import. Is it feasible to make the Import tasks window draggable so you can view complete tasks?
Recently I started to use this function a lot, it really helps me out especially when I make a quick list-to-do out of some email or correspondence, so it's like rapid task entry in MLO or other apps. Funny enough, the more I work with TDL, the more hidden features I discover)
I mean: could I see the task's eclipsed time when it is started?
For example, task A begins eclipse at 2013-5-5 13:42:21， could I find any record of this time in the tool?
I know there is the column "start" there, but this column is not what I am looking for.
Column "start" is the time the task build up, rather than the time the task is excuted.
I could only see the "start" column, and it displays the date. I don't know how to find out the "start time", even when I looked for it in the preferece menu, default task attribute. I wish I could post the pic here.
I figure it out at the bottom.
but it is a pity that it couldn't automatically set the time when the task is started.
As a matter of fact, I guess that we might fill this field out with hand.
Could the time be set when we begin to work?(time spent begins to work)