search

austinvernsonger / keynote-nf

Automatically exported from code.google.com/p/keynote-nf
0 stars 0 forks source link

Allow searching and filtering (hiding or showing) considering the checked state of the nodes #345

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Hello,

It would be useful to show only a few nodes in a tree note.
With the current option, one has to check all the other nodes one by one in 
order to hide them. 
Is there a way to do the reverse, or check all nodes at once?

Thanks.

Original issue reported on code.google.com by jphbru...@yahoo.com on 25 Jul 2010 at 12:02

GoogleCodeExporter commented 9 years ago 
I will include an option to consider the checked state in the search panel. 
With that option, together with the existing option "Filter Tree Note" you will 
be able to do what you need.
The workaround you mention is, of course, no solution.

Original comment by dpra...@gmail.com on 22 Aug 2010 at 11:20

GoogleCodeExporter commented 9 years ago 
My request had to do with nodes visibility, not searching and filtering (my 
summary text must have been changed; my original message said "show only 
checked nodes" I believe).

While it's possible to see only unchecked nodes, the converse ability to see 
only checked nodes would be useful.

It matters if you have 100 nodes and want to show 5, for instance. Right now, 
unless I'm mistaken, you'd have to manually check 95 nodes.

One alternative to adding "Hide unchecked nodes" would be to be able to check 
all nodes at once  and then uncheck the few. 

Thanks.

Original comment by jphbru...@yahoo.com on 22 Aug 2010 at 1:59

GoogleCodeExporter commented 9 years ago 
Of course, summary text have been changed. I have changed it.

I have adapted your necessity to a more general feature. If you have ever tried 
the option 'Filter Tree Note', you have seen that only the nodes satisfying the 
search will be visible; the others will be hidden.

I said that check and uncheck to get nodes hidden or visible is no solution at 
all. Checked state offers you the possibility of assigning a boolean value to a 
node, with a meaning to you: task completed, for example. Making hidden checked 
nodes is then a natural necessity, by that usual meaning (or similar). More 
usual will be that the state of a node is stable, but not your visibility 
intention over that node.

Regards.

Original comment by dpra...@gmail.com on 23 Aug 2010 at 9:39