This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 230849 - Selection events for method parameters (and for methods themselves) in Tigerstripe artifact editor passed to annotations f/work with empty ISelection
Summary: Selection events for method parameters (and for methods themselves) in Tigers...
Status: CLOSED FIXED
Alias: None
Product: Tigerstripe (Archived)
Classification: Technology
Component: Annotations (show other bugs)
Version: 0.3M1   Edit
Hardware: All Windows XP
: P3 normal (vote)
Target Milestone: 0.3M2   Edit
Assignee: Eric Dillon CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-07 05:31 EDT by John Worrell CLA
Modified: 2012-03-01 17:00 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Worrell CLA 2008-05-07 05:31:05 EDT
Build ID: M20080221-1800

Steps To Reproduce:
1. Open Tigerstripe project
2. Double-click a Tigerstripe Entity to open editor
3. Select method-param or method in editor
4. No menu for annotations on right-mouse-click

Debugging shows empty selection coming into annotations f/work - artifact can be identified from "part" but ISelection is empty so no more detail obtainable.



More information:
Comment 1 Eric Dillon CLA 2008-05-07 13:09:15 EDT
Basically, all selections within a tigerstripe editor should be hooked up to provide a proper ISelection.
This is valid for:
- attributes
- methods, method-args.
- literals
- associationEnds.

Now, there is a bit of the "twist" there though, because the Iselection should only be provided if the "selected object" has been saved already. In other words, selecting an attribute on a "dirty" editor should not provide anything, until the editor is saved to avoid building annotations on objects that don't exist or may still be transient.

Re-assigning to myself.
Comment 2 Chris Hartley CLA 2008-10-08 18:31:21 EDT
No problems that this only works on 'saved' artefacts.

Can the priority for this be raised ?
Comment 3 Navid Mehregani CLA 2012-03-01 17:00:33 EST
Has already been fixed.  Annotations can be added from menu in Explorer or by simply selecting it and adding it from annotation view.