With OmniFocus, we can define projects as sequencial or parallel. By default, I define my projects as parallel. But from time to time, I have a project with an action which really needs to be done before any following one: so I mark that project as sequencial, which works OK if there is just one blocking action. But imagine the following case for a construction project:
- Get material M1
- Get material M2
- Do assembly A1
- Do assembly A2
The idea is that I can do A1 and A2 in whatever order as soon as I have M1 and M2. Right now, I have to:
1. Mark the project as sequencial
2. Create a group set to parallel around M1 and M2
3. Create a group set to parallel around A1 and A2
If we had a concept of "this action blocks any following actions until done", I could just create such an action and name it "Check I have all the materials" between M1,2 and A1,2.
Yes, some of you might find that this isn't as clean as the solution using groups. But it would be so much more simpler to put in place and to understand. Any thoughts?
Alex
- Get material M1
- Get material M2
- Do assembly A1
- Do assembly A2
The idea is that I can do A1 and A2 in whatever order as soon as I have M1 and M2. Right now, I have to:
1. Mark the project as sequencial
2. Create a group set to parallel around M1 and M2
3. Create a group set to parallel around A1 and A2
If we had a concept of "this action blocks any following actions until done", I could just create such an action and name it "Check I have all the materials" between M1,2 and A1,2.
Yes, some of you might find that this isn't as clean as the solution using groups. But it would be so much more simpler to put in place and to understand. Any thoughts?
Alex
Threaded Mode