odd behavior creating a action in Context view
 

What I don't understand is what OF is doing when I have a context highlighted that does not contain any actions and I try to add a action in that view. What OF does is create the action in the last context listed (not the one currently selected) and doesn't allow me to set the project for that new action. This is very weird. Is OF supposed to let me add a action in Context view? If so then it should create the action in the selected context even if the context is empty and allow me to assign a project. If I shouldn't be able to create a action in context view then OF should hide the Add Action button. I'd like to see this fixed before I buy the app.

Whats worse, is I tried this where my last context was a sub context, and while the action initially looks like it was created succesfully, when I switch to another context, then switch back, the action is completely gone - no trace. Searched for it and everything - but it just goes poof.

Creating actions in context seems completely broken in the current build.
(96137)

-P

I was seeing this, but eventually found my new tasks (with the project assigned) were placed in the Inbox. It was quite confusing. I expected that creating a task with a context active would automatically assign that context to the task. Cleaning up moved things to the right place, but it's a weird process...probably a bug.

You're right. I found them in the inbox. Interestingly it DOES assign them the context - but the action is still considered unplanned while in your inbox (until cleaned up) so won't show up ANYWHERE in context view.

I would still consider this a bug...

[thats another one for the FAQ - items with context but no project don't show up in context view, this WILL BE an FAQ for the non-strict-GTD who sometimes get things done while they are still in the inbox...]

-P