Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 298773 - [Sequence Diagram] Delete from diagram of combined fragments.
Summary: [Sequence Diagram] Delete from diagram of combined fragments.
Status: RESOLVED DUPLICATE of bug 274808
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.7.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 0.7.0   Edit
Assignee: Thibault Landré CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-04 11:34 EST by Sébastien Gérard CLA
Modified: 2010-06-10 04:55 EDT (History)
0 users

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 Sébastien Gérard CLA 2010-01-04 11:34:12 EST 
It is not possible currently to delete from diagram of "consider ignored fragment". It should be possible. When this bug will be fixed, please chack that DnD from model explorer to diagram works properly.
Comment 1 Sébastien Gérard CLA 2010-01-04 11:36:23 EST 
This is  the case for both combined fragments and consider ingored fragments
Comment 2 Thibault Landré CLA 2010-01-05 10:34:48 EST 
I cannot reproduce this behavior. Can you send us a model or a procedure to reproduce this bug ?
Comment 3 Remi Schnekenburger CLA 2010-06-09 12:37:47 EDT 
Sebastien, 

Is this bug still reproducible for you?

(target milestone set to 0.7.0)
Comment 4 Vincent Hémery CLA 2010-06-10 04:55:02 EDT 
(In reply to comment #0)
> It is not possible currently to delete from diagram of "consider ignored
> fragment". It should be possible. When this bug will be fixed, please chack that
> DnD from model explorer to diagram works properly.

We can not reproduce the "delete from diagram" not working.
The drag and drop, on the other hand, still does not work, but this problem is logged in #274808 - 9/.
If you reproduce it, please provide the detailed steps in #274808.

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