Bug 82687 - [1.5] Inconsistent double-click strategy on annotations
Summary: [1.5] Inconsistent double-click strategy on annotations
Status: RESOLVED DUPLICATE of bug 86971
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: 3.1 M6   Edit
Assignee: David Audel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-12 12:31 EST by Tobias Widmer CLA
Modified: 2005-05-18 07:03 EDT (History)
2 users (show)

See Also:

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 Tobias Widmer CLA 2005-01-12 12:31:48 EST 
20050111: The java editor double click strategy on referenced annotations 
automatically selects the '@' plus leading whitespaces. The action "Open 
Declaration" cannot be used anymore after having double-clicked on an 
annotation reference, since code select takes the '@' into account.
The suggestion is therefore to select the reference annotation name only.
Comment 1 Dani Megert CLA 2005-01-13 04:23:10 EST 
I talked with Martin about this and he agrees that F3 (i.e. codeSelect(...)
should also work in cases like that. And also here:
<caret>@  myAnnotation

Martin also said the AST node contains the full range (@...myAnnotation).
Comment 2 Olivier Thomann CLA 2005-01-13 14:14:54 EST 
The @ must be within the source range of an annotation. Code select should work
only on the annotation name. @ is not part of the name.
I don't find this behavior wrong at all. I am using build I20050104-1600 and it
works as I expect it to work.
Comment 3 Dani Megert CLA 2005-01-13 14:24:03 EST 
comment 0: 20050111
Comment 4 Martin Aeschlimann CLA 2005-01-14 04:29:43 EST 
I also think that code select could be friendly and also accept the '@' as part
of the annotation. Note that the AST annotation node hase a range that starts
from the '@'. 'myAnnotation' is a name that is part of the annotation.
Comment 5 Philipe Mulet CLA 2005-05-17 12:20:52 EDT 
David - is this still an issue ?
Comment 6 David Audel CLA 2005-05-18 07:03:41 EDT 

*** This bug has been marked as a duplicate of 86971 ***