Rob, let me make sure that I'm not misleading you about archiving of recurring tasks. It works fine, the only problem is the archiving of subtasks of recurring tasks.
Gory details follow. When I complete a recurring task, MLO does *not* make a completed copy and then create a new copy. It just resets the dates to the new interval and leaves the task open. (The situation is more complex when the recurring task has subtasks, but that's out of scope for this discussion) Since the recurring task itself is never in "completed" status, it's not a candidate for archiving, so it's not necessary to exclude it from archiving. Btw, this discussion shows a weakness of the uservoice paradigm. The need to manually exclude subtasks of repeating tasks from archiving was a big obstacle for me and was very annoying, until I figured it out. But now that I get it, it's not such a big deal for me. I'm certainly not altruistic enough to devote any of my uservoice votes to fixing it, when there are other things that I really need today. So nobody is representing the needs of the future users. A marketing professor of mine taught that designing your products to meet the needs and wants of your users is a sure path to stagnation, you need to design for your future users instead. -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mylifeorganized?hl=en.
