This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 230738 - Static Code analysis usage flow is inefficient
Summary: Static Code analysis usage flow is inefficient
Status: RESOLVED WONTFIX
Alias: None
Product: editor
Classification: Unclassified
Component: Hints & Annotations (show other bugs)
Version: 7.4
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Jan Lahoda
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-04 14:28 UTC by gena01
Modified: 2013-07-17 16:43 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description gena01 2013-06-04 14:28:28 UTC 
I saw that Static Code analysis got added to 7.4 nightlies recently which I think is awesome. I have been using http://sourceforge.net/projects/phpmdnb/ Netbeans plugin and I love how it integrates into the "Action Items". I usually have it set to show only the currently open file. This allows me to switch between open file tabs and see what sort of stuff I need to fix to make sure i am following the coding standard (PSR2). Current Netbeans 7.4 Inspect implementation seems to be a bit clunky. It makes things really hard to keep "Inspecting" things especially if I am interested in seeing only issues for the file(s) I am currently working on. Refresh only refreshes the existing view for the whatever settings were selected when I selected Inspect. When i change between open files and click refresh it keeps checking the originally selected open file when I selected Inspect option.
Comment 1 Tomas Mysik 2013-06-05 05:16:21 UTC 
Reassigning to the proper component, not PHP specific. Please evaluate, thanks.
Comment 2 Roman Svitanic 2013-07-15 15:47:53 UTC 
In my opinion "Refresh" does exactly what is supposed to do. Imagine situation that you do inspect on some file, than select some file in project explorer and click refresh. It would be confusing if it would run "refreshed" inspect on selected node instead of opened file.

You can set keyboard shortcut for Inspect (ALT+I for example) in options. That would help to achieve you desired functionality.
Comment 3 Roman Svitanic 2013-07-17 13:52:06 UTC 
As described above, mentioned behavior of "Refresh" is desired and intentional. 

When you run Inspect again from Source menu (or keyboard shortcut), all options will remain from previous inspection, but scope will be updated.

I'm closing this as wontfix for now.
Thanks for understanding!
Comment 4 gena01 2013-07-17 16:43:02 UTC 
From my perspective I still need a clean way to switch between opened PHP Files and see the static code analysis for the file I have open/selected. Ideally without having to go through Inspect (Alt+I shortcut) every time i switch between files.