[Ward]

I like the behavior of checkboxes in OmniOutliner:

1. The checkbox on a parent line reflects the state of child lines:
   • empty = no children are checked
   • hyphen = at least one child is checked & at least one is not
   • checked = all children are checked
2. Checking/unchecking a parent line propagates to all children.

OmniFocus outlines look like OmniOutliner but behave quite differently:

1. Checking a parent task marks the parent task and all subtasks as Done.
2. Otherwise, parent tasks and subtasks are independent. Thus, setting all subtasks Done does not automatically set the parent task to Done.

It seems to me OmniFocus checkboxes should behave like OmniOutliner as closely as possible.

Disclaimer: I realize OmniFocus' view filtering may affect the outline semantics in ways I don't yet understand.

[submitted as formal feedback]

[ptone]

See this post:

http://forums.omnigroup.com/showpost...11&postcount=9

-P

[Journey]

Originally Posted by Ward

I like the behavior of checkboxes in OmniOutliner:

1. The checkbox on a parent line reflects the state of child lines:
   • empty = no children are checked
   • hyphen = at least one child is checked & at least one is not
   • checked = all children are checked
2. Checking/unchecking a parent line propagates to all children.

OmniFocus outlines look like OmniOutliner but behave quite differently:

1. Checking a parent task marks the parent task and all subtasks as Done.
2. Otherwise, parent tasks and subtasks are independent. Thus, setting all subtasks Done does not automatically set the parent task to Done.

It seems to me OmniFocus checkboxes should behave like OmniOutliner as closely as possible.

Disclaimer: I realize OmniFocus' view filtering may affect the outline semantics in ways I don't yet understand.

[submitted as formal feedback]

I think Omni Outliner might be better able to implement one's own way of doing GTD better than Omni Focus in its present state. At least with Omni Outliner one can define another column.