Hi Andrey, thanks for considering the idea. 1) Should this inheritance propagated to all subtasks (all levels)?
Definitely. It's very common to have 'container tasks' that serve only to group real tasks. Deeply nested tasks should behave the same as shallow-nested ones. 2) Should the context replace current contexts or should be added? Added. One example to see why this is the case is to have a 'life area' context. You would set the context 'Personal' to the root task and it would propagate to all subtasks. Then, at any point of this 'Personal' branch, you could add the context 'Father Role'. That context also propagates to all of its subtasks (now this subtree has both contexts 'Personal' and 'Father Role'. Then, at some point in the tree, you will have real tasks. Then you could add "@Home" or "@Office". Best regards, Luciano Passuello http://litemind.com ~Exploring ways to use our minds efficiently -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Andrey Tkachuk (MLO) Sent: Wednesday, September 17, 2008 4:27 AM To: MyLifeOrganized Subject: [MLO] Re: Feature Request: True Context Inheritance I will consider option when MLO always inherits Contexts of immediate parent when the parent for particular task is changed in MLO. The questions: 1) Should this inheritance propagated to all subtasks (all levels)? 2) Should the context replace current contexts or should be added? Andrey. On Sep 16, 4:00 am, Luciano Passuello <[EMAIL PROTECTED]> wrote: > Hi Andrey, all: > > Lately, I’ve been playing a lot with contexts and, especially with > advanced filtering, the possibilities are endless. > For some of them (still under test), I’ve found it’s immensely useful > to have tasks inheriting the parent contexts. > I’m sure that others users would have have their own uses for context > inheritance. > > There are already some mechanisms in place for context inheritance in > MLO, for example: > > * In Tool->Options->Behavior, there’s the option to inherit all > contexts from parent when draging and dropping tasks. new parent you > can set to inherit all contexts from parent. > * There’s also “Add all contexts to subtasks” in right click outline > task -> advanced. > > However, even with these two mechanisms in place, I still can’t trust > that subtasks of a particular task will inherit its tasks. > The following cases, for example, don’t enforce the inheritance the > tasks: > > * Cut/Paste instead of Moving. > * Moving the tasks via Shift+Alt+Arrows. > > There’s no TRUE, AUTOMATIC inheritance --- just functions to help you > inherit the tasks when you need. > My point is that until there’s automatic inheritance stricly enforced > by MLO, the whole point of “inherit tasks” is not reliable enough for > those who have their systems depending on this. > > What do you think? > Do any other users find true context inheritance valuable? > > Best regards, > > Luciano Passuellohttp://litemind.com > ~Exploring ways to use our minds efficiently --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MyLifeOrganized" 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/myLifeOrganized?hl=en -~----------~----~----~----~------~----~------~--~---
