Summary: | [1.5] Inconsistent double-click strategy on annotations | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Tobias Widmer <tobias_widmer> |
Component: | Core | Assignee: | David Audel <david_audel> |
Status: | RESOLVED DUPLICATE | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | daniel_megert, martinae |
Version: | 3.1 | ||
Target Milestone: | 3.1 M6 | ||
Hardware: | PC | ||
OS: | All | ||
Whiteboard: |
Description
Tobias Widmer
2005-01-12 12:31:48 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). 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. 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. David - is this still an issue ? |