I ran into same thing and thus chose "yearly" instead of "annually". I think just removing the "Lcase" statement will do the trick.

My personal mindreader.mmap uses the "category" branch to assign the repeat category keyword (e.g. If mindreader sees "mow lawn weekly", it gives it a weekly category that "mark task complete" will recognize). In order to roll that out I'd like to keep the syntax as consistent as possible between the two. Your modifications are more readable (e.g. End of Month instead of endofmonth), so I'd like to roll them into the 'production' version.

What I'd like to do is first add a line of code that looks for legacy keywords and either warns user or (optionally) updates them. Once that is done I'll paste it into the "Dev" version on the wiki.

http://blogs.lefebvre.us/kenneth/2007/06/10/MarkTaskAsComplete.aspx

Thanks for your hard work at putting all these great macros together!

It is very easy to create notes {notes:'text'} or append notes {notes:'text':add}. The problem is it is also good practice to configure ResultsManager to not bring topic notes along to the dashboards as it can slow things down. In that scenario, you might not want to add a note to a dashboard activity and "send-changes" back to the raw map, as it might overwrite an important original note. I believe ResultsManager is probably configured to avoid this problem and thus doesn't send note changes back.

So there isn't a way to append notes to a task using the scripting language?

Curtis

What do you mean by "disappear"? The current scripts don't have any deletion step. The early versions of "dit", "diw", and "dim" might have had a deletion in early versions as I was using it that way on repeating items on dashboards.

There isn't a gyroactivator command for deletion and I found the send keys function wasn't reliable. Some of that may have been due to some documentation errors that are being corrected in the send key code reference. It could probably be done reliably on dashboards (not original maps) using Sax basic command similar to how these scripts accomplish the copy/paste. It would be much more involved to figure out how to surf into the original map and find the task for a deletion.

It would be easy to set the due date to the done date in the dashboard and send the changes back to the original map along with the completion status. Notes don't seem to be sent back using send changes (at least if you have the option turned on to not pull the original notes into the dashboard). That makes sense as you might not want to overwrite the original notes.

Thanks for interest. It is always good to know some folks are giving things a try.

Gyroactivator quits during/after the script runs. Any ideas as to how to go about debugging? It shows up properly in the tracking map but doesn't disappear from the dashboard and only sometimes disappears from the underlying map.

AppName: gyroactivator.exe AppVer: 1.4.0.0 ModName: oleaut32.dll
ModVer: 5.1.2600.2180 Offset: 00033e2c

How hard would it be to either delete the topic from the underlying map or apply the date/notes to the underlying topic as well as the tracking map?

run:macro:'activedocument.selection.copy';
and later
run:macro:'activedocument.selection.paste';

I don't think the current GyroActivator language features would allow what you are proposing. You can select all the completed tasks in one shot {select:complete:100}, but can't easily cycle through them to process them to another map or delete them.

I think a potential strategy is to run a RM dashboard (as suggested above), mark all the completed tasks with a category (e.g. marked-done), cut/paste them from the dashboard to a log map manually, and then filter them from returning to the dashboard the next time with a "NOT marked-done" category filter. They could be deleted from the maps later manually (e.g. by using the MM power filter to select them.). This might not enable the same cross-project daily view that this tag provides unless it is done daily.

Personally, where I've found the most use for the "log it done" approach has been by incorporating the code into 3 tags I use for repeating "put it front of the door" -type tasks (e.g. daily — clear email inbox, daily — exercise; monthly — pay cc bill). Previously I just used these tags to move the start and end date out to next cycle. Using this approach provides the positive reinforcement of showing completions accumulating. These commands work from dashboard (where I usually use it) or on raw map. I've posted these to the library.

Figuring out what project a task is associated within the project map would be difficult using only GyroQ unless you made some assumptions about the project map structure. For example, you could use the central topic name (but that would require use only on the raw map). Perhaps it could prompt the user for the project or area name on the fly. If the script was designed to work only from a dashboard map, it could likely be plucked from the call-out that ResultsManager adds (but then you can't delete it). It might be hard to create a one size fits all solution. Maybe this will draw some lurkers out with some ideas.

Trevor's suggestion of using a "completed" map seems like a workable manual approach. You just need to remember to toggle the "allow completed activities to dashboard" setting between other dashboard uses and make sure you keep track of what you have archived before deleting.

I think pushing tasks to a completion list in real-time or daily with this macro might turn out to be a good motivational game to play (what did I get done today, and were they the right things?). Time will tell.

this is quite useful.
What I would prefer are the following options/changes to that script:
- Delete the finished task in the project map when copied to the log map and
- Sort it in the log map by project or have a separate log map per project.

Would that be possible with GyroQ? I am just a stupid user and have no idea of programming.

Many thanks and regards

Stefan