Quote:
Originally Posted by dal71
I call it an abuse only because the software seems to want it to mean that you *can't* start it until some date in the future; presumably that is why the designers consider such things "unavailable", and treat them identically with actions that really can't be started because they sit behind incomplete actions in sequential projects.
|
It's just a convention that the software follows so that you can use it that way, if you like. You can always see the actions if you show remaining or all actions, so it isn't very insistent that you not look at them; it just won't offer them to you as available.
http://forums.omnigroup.com/showpost...45&postcount=5
Quote:
But, yes, my use is similar to what you say. Only for me it is more like I sometimes/usually don't want to see these things until a few days from now. But I might want to, and I want to do that without seeing things truly unavailable because they depend upon another action that hasn't yet taken place...
Thanks for your thoughts!
|
Don't be in too big of a hurry to assign start dates when using them to sketch out a plan of when you are going to work on individual actions. Maybe only assign them to tasks you are confident you'll start working in the next few days (and of course tasks that you cannot work until the start date arrives). If nothing else, it cuts down on the amount of time you spend fiddling around with start dates instead of actually starting actions :-)