| Project: | Mori |
| Version: | 1.1.3 |
| Component: | Miscellaneous |
| Category: | feature |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Description

[ This issue first popped up in http://www.hogbaysoftware.com/node/811 ]
When a non-leaf node N of a notebook is captured within a smart folder S, then only the node N itself in included in S, but not its own children. I find this quite counterintuitive, because I would usually mean to capture the full subtree.
In comparison: in HBN, when creating an alias of node N, then the alias gave access to the full subtree. Quite intuitive.
To be friend with both interpretations, there could be a switch in the Preferences to tell whether one wants it or not. Or, it could be done as a smart-folder-specific checkbox in the "edit-smart-folder" dialog.
-- Uwe
Updates
Yes. This is an example how frustrating it can be to get simple things done with Mori - frustrating because the power is so near and yet so far! Here's an example: I have a bunch of projects going on, and each one has materials that need to be bought. Naturally, each project's shopping list will be stored as a subtopic under its project topic, but I'd also like to have a master shopping list to take with me when I go out. A smart folder should be just the thing! Create one that looks for "Shopping List", and voila! But of course since the smart folder doesn't show the children of all those shopping lists it's useless. Okay, I can work around it by making an alias of every project's shopping list and place them all in a master Shopping List folder, but that's pretty cumbersome. Of course, Mori's inability to print at all makes the whole exercise somewhat moot :-(
Yes, I'm not sure what good smart folders are without this feature, which at the very least should be a preference option.
This too is one of my biggest frustrations w/ the current smart folders. We are so close to having a near perfect task/ project management tool. But, little things like this make it like a glass ceiling- you can see what you want on the other side but you can't quite touch it.
I concur. This is critical.
In fact, another problem with using aliases to solve the problem julia dee describes is that after you complete each task (or buy each item) you have to now delete the entry in two places. Not really a workable system. I have the seem needs for a global "Next Action" list and a number of other things. In general I want to keep items organized by project but also be able to have a master view of all of them.
I'm interested in this, too, especially because I would prefer to keep my notes organized by search criteria rather than folders and keep everything in just one folder. Then when I need something, I can get it through smart folders, without losing the hierarchy that I do want.
I agree with this feature, and would like to offer an expanded suggestion. When I use a smart folder to find undated items, I'd like the option to specify that it only displays parent items with their corresponding drop downs. For example, I've entered in a dozen things that need to get done on a project. I'd like the option to be able to see a list of those 12 things, be able to date them, and not have to see all of their undated sub-items.