Minor modification: I wrote this as though recurrence was calculated on 
start date but it's on due date. So what you need to do is to take the lead 
time in days and add the number of rest days you want, plus one and set 
that value for the "recurrs [__] days after completion field. In the 
example, lead time (found in the timing and reminder section right under 
due date) is 7 days, plus one rest day plus one (7+1+1) is nine so you 
would set "recurrs [_] days" value to 9.

You can use trial and error - set everything up then go through and mark 
all of the exercises and workouts complete. Pretend that today is the day 
you complete Workout C. When you mark the last item complete, everything 
will be regenerated. Check the new start date - it this when you want to do 
Workout A next? If not, check how many days off you are and add or subtract 
from the recurrs-after value.
-Dwight

On Saturday, August 24, 2013 1:19:40 PM UTC-4, Dwight Arthur wrote:
>
>
>
> On Saturday, August 24, 2013 12:30:44 PM UTC-4, JimboDimbo wrote:
>>
>>  I can't see much value in trying to put dependencies between them all to 
>> chase your tail (dependency cycling).If you miss a day and need to 
>> reschedule, you just need to change the A/B/C Start Dates in the Recurrence 
>> dialog box (Properties, Timing &  Reminder)
>>
>
> Hi, Peter & Ronen.
> I read Ronen's request, to do workout Y 1 or 2 days after workout X is 
> completed as indicating that sometimes he misses a particular day's workout 
> and wants MLO to automatically accommodate that without his having to spend 
> time rescheduling each time it happens. Dependency cycling is an issue but 
> it can be overcome. Here's a step-by-step.
>
> 1. Create a project with a name like "workouts".
> 2. Set the project's start date for today and due date for next week. The 
> due date is not very important, all it means is that if you have not 
> completed three workouts by this date the project will turn red.
> 3. Click on "Recurrence:None" *(under timing and reminders) to bring up 
> the recurrence popup.
> 4. Select "Daily" and then "Regenerate new task [__] days after . . . - 
> fill in the box for *2* days.
> 5. in the Recurrence popup click the "advanced options" button then make 
> sure that the following are checked: "Reset all subtasks to uncompleted" 
> and "Automatically recur when all subtasks are complete" and "do not create 
> a completed copy of this subtask on recurring".
> 6. Create three projects inside of "workouts" - workout A, workout B, and 
> workout C. Be sure the "inherit parent dates" checkbox is set for all three 
> workouts, and that no recurrence has been set up. Check "complete subtasks 
> in order" in the general section (this is optional but I find it helpful).
> 7. In the dependency section for Workout B, set up a dependency on workout 
> A with a delay of 1 day. In the dependency section for Workout C, set up a 
> dependency on workout B with a delay of 1 day. Do not set up any dependency 
> for Workout A.
> 8 Add your exercises as subtasks to each workout, in the correct order.
>
> Done.
>
> If you look at the workouts you will see (if you set the complete-in-order 
> option) that the first exercise in Workout A is green, all the other 
> exercises are black. That means that the first exercise is an "active" 
> task, ready for you to do it right now. If you look at an Active Tasks 
> to-do list in MLO you will see that first exercise on the list. If you 
> don't get to it, it will wait for you and it will still be there tomorrow 
> and the next day until you get to it. Once you complete the exercise, click 
> the box to mark it complete and the second exercise will turn green and 
> show up on your active tasks. If you decide to skip an exercise today, just 
> click it to mark it complete and the next one will show up. When you 
> complete the last exercise, the workout name (workout A) will appear as an 
> active task. Just mark it complete to show that you have finished the 
> workout. That will trigger the dependency for Workout B which will wait for 
> one day (because of your delayed dependency) and then, tomorrow, the first 
> exercise in Workout B will turn green and appear on your to-do list.When 
> you have finished Workout B, mark it complete and one day later, the first 
> exercise from Workout C will pop up. When you complete Workout C there are 
> no dependencies, however you will have completed all of the tasks within 
> the Workouts project, which will immediately go through a recurrence 
> process. All subtasks will be returned to uncompleted status. The new start 
> date (because it says two days after completion) will be the day after 
> tomorrow. One day of rest while everything is inactive due to future start 
> date, then the next day the first exercise in workout A turns green and off 
> we go again.
>
> In this scheme it's important to mark the workouts complete when you 
> finish them. If you leave it hanging and mark it the next day, that will 
> have the effect of telling MLO you want an extra rest day before continuing.
>
> If this is unclear or does not work for you, let me know.
> -Dwight
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"MyLifeOrganized" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mylifeorganized.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mylifeorganized/af23cb2f-876b-4a0e-bab2-ff1541137a6f%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to