Initiate CI run when a Quick Fix executes and triggers a parse.

[daFreeMan]

Justification
I have disabled the Auto-Code Inspection run after a parse. When I'm working through inspections, I don't mind clicking the button to get the CIs to run and the window populated. When I execute a Quick Fix, a parse is triggered, but, since "auto-inspect" is disabled, the CI window is returned empty. I then have to click the button, triggering a parse and the inspection run.

Description
Execution of a Quick Fix should cause the code inspections to run no matter the setting of "Auto Inspect". I'm working on inspections, I don't want to (and shouldn't have to) do any extra clicking or wait for any extra parse runs.

Additional context

[retailcoder]

Indeed. Nice catch!

[daFreeMan]

An additional bonus would be to run inspections when I open the CI window. I'm not likely to open it without wanting to actually see the inspections. (Another request, or can this be tagged on without too much feature creep?)

[retailcoder]

Not sure I like a toolwindow that initiates work just by being displayed, without any other user interactions.

[rubberduck203]

Instead of triggering a whole new parse, why not strategically update the inspections list and parse tree? We know exactly how we’re modifying it, right?

[daFreeMan]

And since we're going to strategically update the inspection results, how 'bout we strategically update the CE every time the <enter> key is pressed? We know what changed there...

😁

[retailcoder]

We know exactly how we’re modifying it, right?

@rubberduck203 as far as inspection results go, we actually don't: it's a clean slate every time.