No Context
 

Today I set my waiting context to 'inactive'. All my `waiting' tasks now appear in the No-Context box, and their number is added to the badge count. Is this a bug or feature (I'm hoping bug).

This is a feature right now -- without this, these actions wouldn't show up in context mode even though you might have an active project depending on them.

You might try flipping off the 'Allows next action' flag on the inspector on that context. Right now this marks the actions as blocked, but really it should just mark them available but skip them for the purposes of determining the next action. <bug://bugs/36902> (Revisit 'allows next action' on Context)

Edit; I should mention that we'd like to make this a tri-state value with something like:

- normal; contexts with this action may be the next action
- skips; ... a following action may still be the next action
- blocks; ... no following action may be the next action

[QUOTE=Tim Wood;26404]Edit; I should mention that we'd like to make this a tri-state value with something like:

- normal; contexts with this action may be the next action
- skips; ... a following action may still be the next action
- blocks; ... no following action may be the next action[/QUOTE]

After some puzzling on this for some time, I'm wondering exactly what the purpose is of the "blocks" value. If this is what is desired:

[code]Sequential project
next action 1 in a block context
action 2 blocked
action 3 blocked[/code]

Isn't this already the equivalent:

[code]Sequential project
action 2 blocked by any incomplete subaction
next action 1 in a skip context (such as waiting for)
action 3 also blocked[/code]

Granted, in the second example, action 2 is an action group. But the goal of blocking is nonetheless possible to achieve with a skip context. Or is my thinking messed up somehow?

Edit:
Whoops! Waiting for is a block context. I guess what we don't have now is a skip context. Which would be basically a non-action, a note that is not attached to any action.

Edit 2:
Whoops again. Waiting for is a skip context, as I thought (it's not set to allow next actions.) So it will block action 2, but not action 3. Sorry about the fogginess -- shouldn't try to think after a long day of research.