I don't think you're misinterpreting. It is a hierarchical listing. My thought comes from my own use case where I'm working with many subclasses which implement empty base class functions and when I get the results I can't tell which hit is hit, if I was able to see the parent node then I would be able to tell the hits apart. I think being able to delete or collapse these would be a good idea, but would require a bit more work than what I had in mind ;) I'll consider the design, I think changing it to a tree would be the best way to get a collapsible listing.
On Wednesday, October 7, 2015 at 4:41:05 PM UTC-4, Terry Brown wrote: > > On Wed, 7 Oct 2015 10:18:06 -0700 (PDT) > john lunzer <lun...@gmail.com <javascript:>> wrote: > > > I implemented a filter which removes duplicate headline matches and I > > added a 4-space indent to body matches which makes a huge difference > > visually especially when there are multiple body matches. > > Great idea, looks good. > > > I plan* to add a "group by parent" check box which will identify the > > parent of each match and then report matches in with an additional > > indentation under the reported parent node. > > Not 100% sure I follow - would the listed hits be collapsible (or > simply deletable would do) so you could zero in on relevant hits? Or > maybe collapse / delete would be a handy way of dismissing irrelevant > hits... I guess I'm interpreting your description as a hierarchical > listing? > > Cheers -Terry > > > *by plan I mean it might happen in a couple months, hopefully > > sooner :) > > > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
