| Summary: | Use of SetCommand with List lead to a wrong result | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Modeling] EMF | Reporter: | Nicolas Guyomar <nicolas.guyomar> | ||||||
| Component: | Edit | Assignee: | Ed Merks <Ed.Merks> | ||||||
| Status: | CLOSED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | ||||||||
| Version: | 2.7.0 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows XP | ||||||||
| Whiteboard: | |||||||||
| Bug Depends on: | |||||||||
| Bug Blocks: | 337408 | ||||||||
| Attachments: |
|
||||||||
|
Description
Nicolas Guyomar
Created attachment 193076 [details]
Patches to address the issue.
It looks like it's important to keep the list of remainingValues that we're using to analyze which objects need to be moved in sync with the moves that will be done by the actual move commands. Could you verify this solves the problem; it makes the test pass.
Thanks for making it so easy to reproduce the problem!
Hi Ed, Thank you for the patch, it solves my problem with the SetCommand. Would that patch be applied for 3.6 M7 ? Regards, Nicolas Guyomar The fix is committed to CVS for 2.7. It will be in the M7 build. The changes are available in EMF 2.7 M7 or an earlier build. |