Yes, indeed that is the solution I was going to post (although technically I would say you found a bug). I have always had an "unfiled" context because it allows me to easily catch when something has not been assigned a non-default context. Note I said "non-default" because the default context does not have to be a negative thing; ie, something waiting for its "real" context. You may elect to use a default context as one you find you always use for many actions, saving the step of assigning it.
-- tomo "Don't think you are. Know you are." - Morpheus On 22-Dec-08, at 6:44 AM, HeX wrote: > > Ah I found the solution myself. Simply creating also a context called > 'unfiled' will help remove that tag when switching an action to > another context. > > /HeX > PS: In case TomO "listens", Maybe it would be a good idea to equip the > default d-cubed template also with a default 'unfiled' context. > > On Dec 21, 11:02 am, HeX <[email protected]> wrote: >> Hi, >> I notice now and again the irritating habit of d-cubed that if you >> create a new action within a project (using the 'action' button) that >> automatically the unfiled tag is set. This is fine at first but it >> would be nice if this could be also automatically removed once I >> set a >> proper context. Is there a simple way to get this funtionality? >> >> /HeX > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GTD TiddlyWiki" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/GTD-TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
