Quote:
Originally Posted by jdh
The new 1.8 behaviour does what you're suggesting, it just seems that it uses the wrong field to actually do it.
|
I like jdh's proposal. It seems to give the most flexibility without overloading the meaning of the existing default context field.
In projects and groups, maybe the existing field should actually be called something like "Default Child Context" and the new field simply called "Context", just like actions.
A parent's context field could then be displayed in the context column of the main outline. That way you save yourself a trip to the inspector to set it for a group; just tab to the context column and enter a value using smart match. Of course, the Default Child Context field would still only appear in the inspector.
-Dennis