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 243292

Summary:	Inspection results usage improvements
Product:	java	Reporter:	RayDeCampo
Component:	Hints	Assignee:	Svata Dedic <sdedic>
Status:	NEW ---
Severity:	normal	Keywords:	USABILITY
Priority:	P3
Version:	8.0
Hardware:	PC
OS:	Windows 8
Issue Type:	ENHANCEMENT	Exception Reporter:

Description RayDeCampo 2014-03-26 14:22:26 UTC

A couple of improvements I would like to see in the Inspect results window to make the workflow of reviewing and fixing results easier:

1) Make it possible to activate the 'Next Problem' button via the keyboard.  This would allow the user to review and fix problems without needing the mouse.  I suggest a keyboard shortcut that is active even when the focus is in the editor, e.g. Ctrl+Alt+Down.

2) Obviously mapping Ctrl+Alt+Up (or the corresponding opposite to whatever was ultimately chosen for 1) to 'Previous Problem' would be desirable as well.

3) Allow bulk handling of issues that can be handled by the editor.  E.g. when migrating a Java 6 code base to Java 7 or above one gets a great deal of 'Can Use Diamond' instances.  NetBeans knows how to fix these, allow me to select them in the results tree, right-click and apply the fix.

Comment 1 Jiri Prox 2014-03-26 14:55:26 UTC

1+2) the default shortcuts are ctrl-, and ctrl-.

3) bulk operation are invoked by Inspect & Transform action (Refactoring menu)

Comment 2 RayDeCampo 2014-03-26 15:03:02 UTC

I did not find the shortcuts in the keymap because they are called 'Next Issue' and 'Previous Issue' in the keymap, whereas the buttons in the Inspect output are labeled 'Next Problem' and 'Previous Problem'.  So I will amend my request to fixing that issue.

I was not aware of 'Inspect and Transform...' - it being under a different menu than 'Inspect' does not make it easy to find and new users.