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.
In: usersguide/javahelp/org/netbeans/modules/usersguide/configure/csh/editor /hints.html there is: <li><strong>Show in problem window.</strong> Java only. Show the hint in the Output window as a problem.</li> I am afraid this is not correct, there is no such option in the GUI (it is in the code, but is disabled and is not shown to the user). I think this point should be removed from the helpset.
I vote for enabling it and showing it to the user - I could definitely use this feature. As the only Netbeans user in my group, I'm always the guy committing "violating" code to our source repository because, unlike Eclipse users, I can't really see all their violations unless I happen to be looking into the gutter of each changed file.
Well, there is a checkbox for that in the panel, but nothing is bound to it, so it is not just making the checkbox visible. Currently, Source/Inspect can be used to see the warnings.
(In reply to comment #2) > Well, there is a checkbox for that in the panel, but nothing is bound to it, so > it is not just making the checkbox visible. Currently, Source/Inspect can be > used to see the warnings. [Sorry for the discussion in two bugs, but I just wanted to make sure there's no loss of information]. I don't see how Source/Inspect is a good substitute. If I've modified 30 files in a project of almost 5000 files, why would I want to run Source/Inspect on the whole project just to see whether I've committed any violations in the 30 modified files? Even with the bug fix in Source/Inspect, I'd have to wait 5 minutes - and then my violations would likely be obscured by those others may have introduced into the project. There should be another Source/Inspect option for only inspecting modified files or, better yet - from a workflow perspective - allow this to be integrated with the output window (I'm already looking at that every time I build - to have to manually do Source/Inspect is really clumsy. That's why I looked forward to the feature described in the Help). Should I file an enhancement bug for this or is there already one (perhaps resurrect the one that killed off the Preferences->Editor->Hints option?)
Ok, I removed the reference to that hint. If anyone implements it in the future, please let docs know.
Marking this for 7.3 unless someone thinks this is worth putting in the 72 patch. Not sure what the keyword for that is. Also, really, this is not a P2 bug.
As this one is closed/fixed by removing the reference in the help, should I open a separate enhancement bug to actually have this feature in 7.3?
Thanks for fixing that. I think it would be worth to push this into 7.2, given how simple the change is: http://hg.netbeans.org/main/rev/921523f8f53e Jirka, what do you think? I can go through the HR process, unless someone else wants to do that.
(In reply to comment #6) > As this one is closed/fixed by removing the reference in the help, should I > open a separate enhancement bug to actually have this feature in 7.3? Yes, the doc issue and the enhancement should be separate issues. Please file the enhancement bug.
verified in trunk
Merged to release72: http://hg.netbeans.org/releases/rev/7f12ba5c549f
Integrated into 'releases', will be available in build *201206212341* or newer. Wait for official and publicly available build. Changeset: http://hg.netbeans.org/releases/rev/7f12ba5c549f User: jeff_rubinoff@netbeans.org Log: removed unimplemented hint Issue #214452 - Incorrect claim in editor/hints.html
Integrated into 'main-golden', will be available in build *201206220002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/921523f8f53e User: jeff_rubinoff@netbeans.org Log: removed unimplemented hint Issue #214452 - Incorrect claim in editor/hints.html
verified in 7.2