Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 320339 - When class diagram is opened, 'Remove from Diagram' action is disabled
Summary: When class diagram is opened, 'Remove from Diagram' action is disabled
Status: RESOLVED FIXED
Alias: None
Product: Tigerstripe
Classification: Technology
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 0.5M0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-19 19:19 EDT by Navid Mehregani CLA
Modified: 2011-02-23 18:04 EST (History)
0 users

See Also:

Attachments
Screenshot (40.54 KB, image/png)
2010-07-19 19:20 EDT, Navid Mehregani CLA 		no flags Details
View All 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 Navid Mehregani CLA 2010-07-19 19:19:50 EDT 
Build Identifier: 

When class diagram is opened and user immediately right clicks on their artifact, the 'Remove from Diagram' action is disabled as indicated in the attached snapshot

Reproducible: Always

Steps to Reproduce:
1. Create a new class diagram
2. Create an Entity in the diagram
3. Save and close the file
4. Open the file
5. Right click on the Entity.  Notice that 'Remove from Diagram' is disabled.  If you click anywhere in the diagram and right click on the artifact again, the action will be correctly enabled.
Comment 1 Navid Mehregani CLA 2010-07-19 19:20:09 EDT 
Created attachment 174689 [details]
Screenshot
Comment 2 Navid Mehregani CLA 2010-12-06 15:31:40 EST 
Scenario outlined in comment#1 has been resolved.  However, extends relationship cannot be removed from diagram.

Try the following:
Create two entities in a class diagram
Create a Extends relationship between the two entites
Right click on Extends, notice that 'Remove from Diagram' is disabled.
Comment 3 Navid Mehregani CLA 2011-02-23 18:04:36 EST 
Marking as fixed.
Another defect will be filed for issue noted in comment#2.