Mark Task Complete Update
If you are using the "Mark and Log Task Done" macro (a.ka. "mtc" tag or mark-task-complete.mmbas), please download the updated version the macro from the wiki Macro Library.
The previous version of the macro acted on the currently selected tasks and got confused if you changed the selected task while it was running. That problem has been mostly addressed now although you can still confuse it if you change the selection just as it is calling the ResultsManager set-task-complete macro.
While testing this bug fix this evening, I noticed that my "completedlog" map was missing a lot of my history and uncovered a larger bug in the way that the macro was creatign the completedlog.mmap initially.
On Error GoTo X
Set tmap=Documents.Open(GetPath(mmDirectoryMyMaps)&"CompletedLog.mmap","",False)
If Err.Number>0 Then
X: Err.Clear
Set tmap=Documents.Add(False)
tmap.SaveAs(GetPath(mmDirectoryMyMaps)&"CompletedLog.mmap")
End If
The program would try to open the map, and if it encountered an error, it assumed the file didn't exist and created a new one. The problem is that if it experienced an unrelated error at this stage, it would overwrite the existing map.
In retrospect, this was a sloppy way to handle the initial file creation, but it seemed to work OK in the early days when the entire program was just a line of code in a small GyroQ tag. My guess is that v7 gives occasional file errors that didn't occur in v6.
If you are using the program, please update to this latest version ASAP and check your CompletedLog to see how far back it has data.
I recommend retaining your completed items in your maps in addition to the completedlog. I keep mine in a floating topic called "completed" so that they don't clutter the main branches. I also highly recommend setting up your computer with backup software to do nightly backups onto a USB drive with version retention.
Stumble it! 
Entries 
ActivityOwner said,
October 11, 2007 @ 7:32 am
Note that the other issue with the original code was lack of a "On error goto 0" after file block to reset the error trap. It looks like errors occuring further down in the code would jump back to this location.
gmmazza said,
November 3, 2008 @ 12:31 pm
Hi, I been trying to use this, but it left the task in the log map without reference to what project that refers. Or I'm using wrong? Could be possible to recreate all the structure of the hierarchy in the complete log? or make the complete to a topic inside the project, lest say as a first child of the project, grouped there? Let me know by email if is needed more explanation of this, I know I'm not very clear explaining things in English!. Thanks!
ActivityOwner said,
November 3, 2008 @ 9:24 pm
mark task complete just copies the completed task from the project map to the log map and places it in the tree under the year/month/date. It would be a more complex and time consuming to try to organize by project there. There is a also an option to also save the completed topic to floating "completed" topic in the project map.
It sounds like you are suggesting having the option for "completed" topics under each project in a multi-project map. That's actually a pretty good idea. I've been finding that my map "completed" topics are getting very big. It would be better if the completed tasks stayed with their own project. I often use 1 map/project but there are several maps with multiple projects where this will come in handy and be more educational (e.g. to assess repeated task completion frequency).
I was worried this might be a big project to implement, but I think I've got it working. Download the latest version from the wiki and give it a try. I've made this the default behavior.
gmmazza said,
November 4, 2008 @ 6:49 am
Thanks!, that's was exactly what I meant!. I find it very useful in exactly that scenario, the multi-project map. I never thought that this will become that fast!. I still find the log map a little bit problematic to review, maybe you can add a link to the original project, something like the dashboards do? I understand the problem with the recreation of the hierarchy. Thanks again for so fast implementation! Thanks a lot!.
ActivityOwner said,
November 4, 2008 @ 8:30 am
I wouldn't want to overwrite the current link on the task (if it has one) with a link to the project map. It would have to be implemented as a callout topic similar to what is in the dashboards.
I also have never figured out how to set a link back to a particular topic in a map (they way dashboard tasks link to their originals). Linking to a source map wouldn't be too bad, but it would technically need to allow for the source map being a mindjet connect space.
It should be feasible to do by making some edits to the copytocompletedlog function. I will try to have a look at it this weekend.