Bug 513758 - [null] JDT null analysis "Annotate" feature does not provide feedback for user error
Summary: [null] JDT null analysis "Annotate" feature does not provide feedback for use...
Status: REOPENED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.7   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
: 513759 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-03-16 09:40 EDT by Matthew DOnofrio CLA
Modified: 2024-04-12 09:22 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew DOnofrio CLA 2017-03-16 09:40:16 EDT
When I choose "Open Declaration" to a class file (with source attached) and attempt to invoke "Annotate", nothing happens; there is no error or immediate feedback indicating the cause of my error.

I discovered that this dialog can only be invoked while the cursor is positioned within a method parameter or a return type. But this took some trial and error on my part. An indication informing the user of correct placement would go a long way.
Comment 1 Stephan Herrmann CLA 2017-03-16 10:32:56 EDT
Annotate is designed as a point-and-click command. I simply wasn't expecting s.o. to try annotation the whitespace somewhere in that file.

Somewhere we have a bug, that the command shouldn't even be visible/enabled if not applicable. You may search for it in component JDT/UI in order to revive it.
Comment 2 Stephan Herrmann CLA 2017-03-16 10:48:42 EDT
*** Bug 513759 has been marked as a duplicate of this bug. ***
Comment 3 Eclipse Genie CLA 2020-04-30 00:39:41 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Stephan Herrmann CLA 2020-04-30 08:11:35 EDT
No, genie. Let's please not drop this ball entirely.

Most of this will actually happen in JDT/UI - only if existing information turns out to be insufficient JDT/Core will need to help.
Comment 5 Eclipse Genie CLA 2022-04-22 12:28:18 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 6 Eclipse Genie CLA 2024-04-12 09:22:26 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.