[whpalmer4]

Originally Posted by labete

I think it would be useful to have some kind of flag that you have orphaned actions, after dropping a context. This would not need to be the No Contexts bin, but if the count is positive, it should tell me what the actions are.

What would you think would be the best way for OF to handle these orphaned actions?

I guess I don't think of them as orphans. If you go to context mode and change the selector over the sidebar to All Contexts or Dropped contexts, they are still there in the database, and if you want to look for them, that's a suitable method. Perhaps a warning when you drop the context that it will hide a bunch of actions might be appropriate, similar to the warning you get when you try to delete a project that has some hidden actions.

[labete]

I think what threw me was the 'No Context' count being there, but nothing actually in that bin. If that wasn't there, and there was a warning as you describe then the chance of missing actions like that would avoided.

[Lucas]

In 1.7.4 r. 118993, I have No Context with a very big number next to it, but nothing listed when I clicked on it, including when I had the All Items perspective selected. I tried to follow the instructions in this thread, but I couldn't find any actions listed next to any dropped contexts either. Does anyone see something I'm missing?

[labete]

Is there anything in the other selectors that could be restricting the actions you can see? What is the status filter set to?

[kaijin]

Originally Posted by Lucas

In 1.7.4 r. 118993, I have No Context with a very big number next to it, but nothing listed when I clicked on it, including when I had the All Items perspective selected. I tried to follow the instructions in this thread, but I couldn't find any actions listed next to any dropped contexts either. Does anyone see something I'm missing?

In context mode, make sure Status Filter is set to Remaining. If it's set to Available you might see a discrepancy between the tasks displayed and the count badge. If that doesn't solve the issue…

I've not tested 1.7.4 r. 118993, yet, but the release notes indicate:

Since the No Context group in 1.6 and later only displays actions which actually have no context (not those which have an invalid context), actions assigned to a dropped context will now appear in that context's count rather than in No Context's count.

According to this, no tasks assigned a context—including dropped context—should be included in your No Context tally. Perhaps you're experiencing a bug in the sneaky peek build. You might want to use Help > Submit feedback.

[Ken Case]

Originally Posted by kaijin

Perhaps you're experiencing a bug in the sneaky peek build. You might want to use Help > Submit feedback.

Yes, sorry, this is a bug which was introduced in yesterday's sneaky peek build; I'm seeing it in my database as well. (It's no longer counting actions from dropped contexts, but I suspect it's counting actions without contexts from inactive projects—projects which are normally excluded from context mode.)