Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 343106 - [ActivityDiagram] Element are blocked in interruptible region
Summary: [ActivityDiagram] Element are blocked in interruptible region
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Diagram (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Vincent Hémery CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-18 04:28 EDT by Fabien Gautreault CLA
Modified: 2013-03-28 05:02 EDT (History)
3 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 Fabien Gautreault CLA 2011-04-18 04:28:34 EDT 
Build Identifier: 20100617-1415

[ActivityDiagram] If user create an element in the interruptible region, it's impossible to drap&drop it out of this region. Seems that small region have been created in the interruptible region. When user try to take the element out, a scrollbar is created and the element is only deplace inside this region.

Reproducible: Always

Steps to Reproduce:
1.Create an interruptible region
2.Create an element inside
3.Try to take this element out of the interruptible region
Comment 1 Vincent Hémery CLA 2011-05-19 03:06:10 EDT 
Hello, lots of work on ActivityGroups have been committed during last months.

The bug you describe looks to me like it exists on older versions but should be corrected on trunk if I am not mistaken.

Which version of Papyrus are you working with ?

If you are working with an Indigo version, can you try and reproducing it after updating your platform with the latests 0.8.0 Stable Build ?
(available on http://www.eclipse.org/modeling/mdt/papyrus/downloads/index.php or on update site http://download.eclipse.org/modeling/mdt/papyrus/updates/milestones/0.8)
Comment 2 Sébastien Gérard CLA 2013-03-28 05:02:32 EDT 
This bug is no more reproductible. Bug closed.