The Omni Group
These forums are now read-only. Please visit our new forums to participate in discussion. A new account will be required to post in the new forums. For more info on the switch, see this post. Thank you!

Go Back   The Omni Group Forums > OmniFocus > OmniFocus 1 for Mac
FAQ Members List Calendar Search Today's Posts Mark Forums Read

 
Contexts on Hold Thread Tools Search this Thread Display Modes
I placed my @Waiting context "On Hold" by unchecking the "Active" status in its contextual menu (or so I thought).

However that prevents the ability to assign an action to @Waiting.

Hovering over the inspector button shows that the context is not on hold, it is "dropped".

I guess I should have figured that out - instead of the "pause" badge, it had an "x" badge.

So - how do people handle @Waiting - just assign the @Waiting context, and leave it active, and know it really isn't?
 
I keep it active, and check it every now and then to see whether I need to nudge someone I'm waiting on.

I put it at the end of my context list, so that when I am showing all active contexts, I don't see the @waiting context's actions unless I scroll down.
 
Quote:
Originally Posted by brianogilvie View Post
I keep it active, and check it every now and then to see whether I need to nudge someone I'm waiting on.

I put it at the end of my context list, so that when I am showing all active contexts, I don't see the @waiting context's actions unless I scroll down.
I keep it active, too, and I set the "Blocks Next Actions" option on the Waiting For context so that these delegated items will never appear in my to-do lists, which are based on actions that are "next" or "available".

This allows you to create a Stalled Projects list that shows projects with no next actions or that are sitting there waiting for someone else to do something. (One quirk: you have to set this Stalled Projects list to show "Remaining" actions, since "Next" or "Available" will exclude the blocked Waiting Fors.)
 
Quote:
Originally Posted by joelande View Post
I placed my @Waiting context "On Hold" by unchecking the "Active" status in its contextual menu (or so I thought).

However that prevents the ability to assign an action to @Waiting.

Hovering over the inspector button shows that the context is not on hold, it is "dropped".

I guess I should have figured that out - instead of the "pause" badge, it had an "x" badge.

So - how do people handle @Waiting - just assign the @Waiting context, and leave it active, and know it really isn't?
Are you talking of an earlier build? I just checked this, and I able to assign an action to @Waiting when it is 'On Hold'. And anytime i give an action the context @Waiting all future actions (for sequential project) become unavailable as they should. Am I misunderstanding something?
 
 


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads
Thread Thread Starter Forum Replies Last Post
Fleshing out some OF Behaviors: On Hold, Project Contexts gattaca Applying OmniFocus 1 2013-03-11 04:11 PM
Why set contexts on hold? Revearti OmniFocus 1 for Mac 6 2013-02-08 05:57 AM
Nested On-hold Context + On Hold Context Filter: expected results? ringods OmniFocus 1 for Mac 9 2010-10-21 06:51 PM
Waiting/On Hold contexts make tasks unavailable andreyb OmniFocus for iPhone 4 2009-07-18 08:33 AM
Do Actions On hold force the entire Project to be On Hold? MarkSealey OmniFocus 1 for Mac 2 2008-02-26 06:27 AM


All times are GMT -8. The time now is 07:13 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.