Thread: Dependant tasks
View Single Post
  #4  
Old 01-11-2008, 04:55 PM
lazlo24 lazlo24 is online now
Registered User
 
Join Date: 12-10-2006
Posts: 23
Dependant tasks

Hi ashwken

I understand what you are saying but this basically means that I as the user must define what shows up in the search, which is what I currently have to do now.

I current have a flag for @next action (Yes it is GTD) which I set to yes when the task is active. What I want to do is program a sequence of events and only have the current and live one visible in the search rather than having to mark off the current one as done and then identify what the next task will be and set that flag. Yes, I guess I am lazy but I like to do all my thinking in one session then switch into 'do' mode where no decisions are made but work is just 'done' as programmed.

I see Quant understands my desire for this. This behaviour is exceptionaly useful when setting up a project that has a fixed sequence.

I think I may have hit a boundary.

Thanks
Lazlo24
Reply With Quote