It is fixed now in the latest setup.exe and in the source code on the wiki.

Hans and I used mindjet connect to collaborate on developing the setup.exe and I bought a 2-user account for my wife's business to play with for this year. For personal cross-computer use I've been using dropbox rather than mjc maps.

When I run the Repeating Things Done macro on Catalyst maps I get a runtime error. Anyone else using Catalyst (Mindjet Connect) maps?

What I tend to do for "yearly" projects is create the subsequent year's task or project at the completion of the previous year, set the start date, and link it into the map central so that it comes up. Examples include holiday shopping, major birthdays, taxes, house maintenance tasks, etc. I think for your example you could probably select all the task and mark them incomplete as once. If you were operating in this mode you would want to set the "movetocomplete" option to false.

I have projects that repeat yearly (e.g. my taxreturn). These projects are defined as lists and for each of them I have defined the steps to perform to complete the project. Of course I don't want to reinvent the wheel next time, so also the tasks in the project have a yearly repeat defined.
When I then mark the first task as done, the next occurrence is correctly calculated but RM doesn't pick up the next task because the first task is still there (be it in the far future).

The way around this is if I physically move the first task to the bottom of the list.
As long as this is done consistently, the reflects the order in which the sub-branches need to be completed perfectly.

Is this somethin other people also use yearly projects? If so, my suggestion is that the MTC-macro checks to see if the parent is a (list) and if so it moves the task that is being marked as completed at the bottom of the list of its peers (like a cut and paste)

If not, I'd be interested to know how other people use these repeating projects … maybe I'm over-complicating things :)

Hope this helps …
Marco

When I use the macro from my dashboard, it doesn't produce the same results as running from the context of the hosting map. The task isn't removed from the original map and it maintains a link back to the original task from the completed log map – so hyperlinks on the activity are not copied across (since you can still link). Is this by design, or are there technical reasons?

I wondered how people were using this macro in practice? I like the idea I just don't seem to be working in way which really gels with the macro which made me wonder whether I'm missing something?

Regards
Darren

Documentation help is welcome. The easiest way would be for you to create an account for yourself on the wiki and just start adding/editing from here:

http://wiki.activityowner.com/index.php?title=MindReader

Note that "Mark Task Complete" is a separate program covered here:

http://wiki.activityowner.com/index.php?title=Mark_and_Log_Tasks_Done

Have you considered adding a fortnightly or eachfortnight to allow for activities that must be done every two weeks? For example, a pay officer in Australia could pay employees every two weeks.

I am considering writing a guide to using MindReader and make it available to you. Would that help you or hinder you?

Rennie

For your example task, you would want to type

q Call Robyn for birthday [~eachyear #25/5/2008#]

The repeating code is stored in the category field (~category) rather than the context (@context) field. That's why the macro isn't seeing your example as a repeating task.

For activities that repeat on a fixed date (like birthdays and bill payments), eachweek, eachmonth, and eachyear are used. For activities that repeat relative to when you did them last (like haircuts and lawn mowing), "weekly", "monthly", "quarterly", and "yearly" are used.

http://wiki.activityowner.com/index.php?title=Mark_and_Log_Tasks_Done#Syntax

Note that until last night there was a bug in the new "move to floating completed topic" portion of the macro that caused it to move repeating tasks to the completed branch, even if they were coded correctly. I hadn't noticed as I usually mark repeating tasks done on the dashboard. It is fixed now.

"Advance" is a new MIndReader keyword that is the opposite of "delay" that allows you to pull forward the start/due date of a future task using "m". I just uploaded last evening and hadn't edited it into the wiki yet.

I have been experimenting with the latest "repeating things done" changes and have run into some problems.

In Gyroq
If I enter: q Call Robyn for birthday [@yearly by #25/5/2008], an activity is correctly created.

Then if I enter d followed by Enter key the task in completed and moved to the "Completed" floating topic. However, the task fails to repeat and the dates change to today's date.

I have also noticed that completing tasks after the original set date sets the next year task to the current day (not the fixed day). For example, preparing a document for 25th April, but completing it by 20th April repeats the task on 20th April on the next year.

I have tried to find an explanation for the new "advance" feature but found nothing.

I really like this set of macros and tags, but must say it is a little frustrating trying to work out the changes.

Thanks

Rennie

An updated version is available in the macro library on the wiki here:

http://wiki.activityowner.com/images/f/f7/Mark_task_complete.mmbas

You can see the code changes in the wiki revision history:
http://wiki.activityowner.com/index.php?title=Mark_task_complete-DEV.mmbas&diff=580&oldid=334

Thanks again,

AO

I will have a look at bug tonight. Perhaps a bug crept in with v7.

Comments are best place for this stuff. The only problem is that for tools that evolve over time there are usually several posts so things do not have a clear home.

I have a forum setup for the site if needed. Would people find that useful?

Instead of first testing

If isdb

and then testing

If (Not isdb) And sacrm

You can do a single test

If isdb Or sacrm

This avoids repeating the same MacroRun statement twice with the risk of having them not match.

Again, very minor point and does not change the functionality.

George Wyner

p.s. if there is a better place for posting these very minor comments please let me know (don't want to detract from the more substantive discussion).

I am trying to enable the 'add completion notes' for raw maps. I tried setting sacrm=True in the macro file.

I created a subactivity of a project and tried marking it complete using Alt C,v and a completion note was added to the map. I repeated the process using the mark_task_complete macro (which I have mapped to AltC,l) and no note was added.

Is logging working for others? (in which case this must be something about my environment)

Is the correct way to change the options to change the True/False value of the option settings in the code (as I did)?

Thanks!

George Wyner

I'll try to add something more to the wiki, but in the meantime, this link provides some good background:

http://mindmanager.wordpress.com/2007/06/19/how-to-use-macro-files/

I'm considering zipping up the main macros from the site along with a gyroQ.ini file with all the main tags so users could get everything installed or upgraded at once.

Thanks to each of you who contribute to this helpful resource.

Don Callihan

I am also finding the "routine" support this script provide very helpful. Ever time I'm marking a random task complete I ask myself it is actually a "repeating task"? I find many things are. For some I create the next version manually (e.g. "Holidays 2007"). In other cases adding the right category entry and leaving the task in place is the right approach.

One of the things I wanted was precisely to address routines. Until now I couldn't find the answer. But this macro does it! Thanks!

I've been testing MindReader macros and tags. I must say that it took me a while to understand how the tags worked, but I eventualy saw the light.

In relation to this macro, I installed it easily and it is working properly. But while I was testing the frequency categories, I noticed that "endofquarter" doesn't work for me. I rechecked my spelling and it was right, so I don't know what it is.

Although I have lots to learn yet, I find MindReader absolutely great. Thanks!

I also changed the "code" for tasks that repeat every two days from "bidaily" to "everytwo". The bidaily text string was getting recognized as "daily".

I'm trying to consolidate background information on the script on the new wiki page:

http://wiki.activityowner.com/index.php?title=Mark_and_Log_Tasks_Done

Note that a new version was uploaded recently that allows the repeat items to be checked off from a dashboard. The previous version lacked the "send changes" macro call to communicate the new dates back to the underlying maps.