Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request for Code Inspection, group by By Location. Collapse ALL inspections. #3960

Closed
PeterMTaylor opened this issue Apr 24, 2018 · 2 comments
Assignees
Labels
enhancement Feature requests, or enhancements to existing features. Ideas. Anything within the project's scope. feature-inspections user-interface This issue explicitly relates to the visible interface of Rubberduck.
Milestone

Comments

@PeterMTaylor
Copy link

Using Version 2.2.6685.5179 (2.2.0.3137-pre) resuming what I meant to start again as a small testing on a cDataset sheet I have to work on. This file contains the project summary of 47 modules / 35 classes / 6 forms / 117 Document objects (sheets) that needs refactoring to adapt proper coding practices that RD considers best. With the Code Inspection grouping set to "By location". Just one little annoyance with Code Inspections I want to document here is a request to collapse ALL inspections in the tree so all is closed and pick one I am working to focus.
rd capture need collapse all option for tree

@Vogel612 Vogel612 added enhancement Feature requests, or enhancements to existing features. Ideas. Anything within the project's scope. user-interface This issue explicitly relates to the visible interface of Rubberduck. feature-inspections labels Apr 24, 2018
@retailcoder
Copy link
Member

One problem is that the UI is not really a tree - it's a custom grouping grid XAML control that we reuse in several places; I suppose we could enhance the control with better grouping capabilities, but ultimately IMO the inspection results toolwindow is in itself the problem... Can't wait to be able to simply remove it!

Perhaps a module filter could be useful and easier to implement? A bit like how inspection settings can be filtered by inspection name, results could be filtered by module/procedure name?

@PeterMTaylor
Copy link
Author

Sounds good. Perhaps a performance benchmark of some form (thinking perhaps in minutes manually closing all inspections within one project) can be made before changing to a module filter so a comparison be realised.

@comintern comintern self-assigned this Jan 16, 2019
@Vogel612 Vogel612 added this to Done in Release 2.4.1 Feb 28, 2019
@Vogel612 Vogel612 added this to the 2.4.1 milestone Feb 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature requests, or enhancements to existing features. Ideas. Anything within the project's scope. feature-inspections user-interface This issue explicitly relates to the visible interface of Rubberduck.
Projects
No open projects
Release 2.4.1
  
Done
Development

No branches or pull requests

4 participants