Todo explorer organization at the project level, not stop at module level

[SmileyFtW]

Has it ever been considered to group all of the to do items into project level when grouping by location instead of the top level groupings be at the module level?
Something like this:

[comintern]

I can certainly look into what would be involved with this. I'm in the process of going through the UI and unifying the look and feel of similar UI elements, and based on the "existing" screenshot this could probably stand a quick refresh if for no other reason than the toolbar styling.

Outside of multi-level grouping for locations, are there any other groupings that might make this more convenient to use? It could probably use an auto-filter, but that's a different issue.

[SmileyFtW]

Since I am new to all of this and just now beginning to really try to use the functionality I don’t know that I have much to offer (yet 😊). I am trying to avoid a whole bunch of little-nit kind of suggestions submitted singly, so I will think on it and try to wrap anything into a more comprehensive set of suggestions. I know that when I first started using the ToDo explorer I thought it a great idea, but struggled a little with using it effectively – it’s a new user thing rather than a thing that needs an overhaul to suit *me*… LOL. I’m still learning. Thanks for everything! David From: comintern <notifications@github.com> Sent: Sunday, February 10, 2019 12:42 PM To: rubberduck-vba/Rubberduck <Rubberduck@noreply.github.com> Cc: David <dgmsmiles@gmail.com>; Author <author@noreply.github.com> Subject: Re: [rubberduck-vba/Rubberduck] Todo explorer organization at the project level, not stop at module level (#4788) I can certainly look into what would be involved with this. I'm in the process of going through the UI and unifying the look and feel of similar UI elements, and based on the "existing" screenshot this could probably stand a quick refresh if for no other reason than the toolbar styling. Outside of multi-level grouping for locations, are there any other groupings that might make this more convenient to use? It could probably use an auto-filter, but that's a different issue. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4788 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AoQ_F020DZpGjzsSafQiNefo5udjmdmrks5vMGgMgaJpZM4azMzS> . <https://github.com/notifications/beacon/AoQ_F-cjqJXGVDjy76WPNbUUymK5NE_Qks5vMGgMgaJpZM4azMzS.gif>

[SmileyFtW]

Kinda related, but maybe not: When expanding or collapsing the up/down arrows, why does the entire display expand/collapse instead of just the selected node. This implementation seems to be throughout RD. All other implementations I am familiar with don't operate the way RD does. If expanding/collapsing the entire tree is the desired action there is usually an expand/collapse all somewhere. Selecting a single node expands/collapses that single node.

[Vogel612]

What you mention in your last comment is already covered under #4849

[SmileyFtW]

Thanks!