Hmm, I can see your original issue, but the commant from Jonas is valid: if you save the file and reload (ignoring the "unsaved changes" message), the new action is correctly converted to a project. So while a bit of a pain to do the reload, it is not a show-stopper.
I'll dig into the code and see what the heck is going on here. I am really surprised nobody has noticed this in all this time. "Projectify" is clearly not a popular feature! -- tomo On Nov 12, 8:25 pm, Marcelo F Andrade <mfandr...@gmail.com> wrote: > On Thu, Nov 11, 2010 at 11:03 PM, jonas thomas <jonasthomas...@gmail.com> > wrote: > > I seem to be getting experiencing the same phenomena. But... If you close > > D3 and re-open all seems well (for me anyway). > > I've never seem to have the need to projectify. > > It seems if you just have an action you can assign a project to it. > > > It seems like projectify takes and action out of an existing project and > > creates a new one. Is that it? > > Well, I'm not sure, but I guess projectify is just an easy way > to turn an action (you see is gonna take more than one step) > into a project. > > This is a boring bug, because in this case I have to copy the > text, delete the action tiddler, create a project, paste the text > and finally create the action steps for the project. > > I don't know if just changing the tag 'action' to 'project' have > the same effect... > > Cheers. > > -- > MARCELO F ANDRADE > Belem, Amazonia, Brazil > > "I took the red pill" -- You received this message because you are subscribed to the Google Groups "GTD TiddlyWiki" group. To post to this group, send email to gtd-tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to gtd-tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/gtd-tiddlywiki?hl=en.
