As far as which rule set is used, you get to pick that (and you can create custom rule sets in Options -> Code Analysis). The main reason we don’t update the list on the fly is simply resources/speed. Basically, if we were to update that list as you type, that’s an extra window that needs to be painted, extra structures that need to be populated, … and we just don’t want to slow down typing. The thought was that the blue “squiggles” and the gutter icons would be enough of an indicator as you’re making your on the fly edits.
From: Peter Lang [mailto:bounce-PeterLang@toadworld.com]
Sent: Monday, March 07, 2016 10:22 AM
Subject: RE: [Toad for Oracle - Beta Discussion Forum] How to work with Code Analysis?
RE: How to work with Code Analysis?
Reply by Peter Lang
A shortcut would help, but I’m not sure if this is ideal.
I certainly don’t have enough background information (e.g. when which rule sets are used), but since the violations are already highlighted in the editor on-the-fly, it would be great to have a list of all highlighted violations that change when editing code. Maybe something like the Eclipse Problems View:
Looks like those two features are more separated than I would have expected, though.
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Unsubscribe from Toad for Oracle - Beta notifications altogether.
Toad for Oracle - Beta Discussion Forum
this post as spam/abuse.