diff options
| author | Christian W. Damus | 2018-05-08 14:42:26 +0000 |
|---|---|---|
| committer | Nicolas FAUVERGUE | 2018-06-05 09:31:15 +0000 |
| commit | 193b89ef7c445558bd1af39025906ea6743dca77 (patch) | |
| tree | be1238bece6665363fb2660b2ce282dd27a92775 /releng/toolsmiths/targetPlatform/eclipse/org.eclipse.papyrus.toolsmiths.eclipse.targetplatform.target | |
| parent | 9ff5fff7785695f43ee84facab4ae4f02800bb6f (diff) | |
| download | org.eclipse.papyrus-193b89ef7c445558bd1af39025906ea6743dca77.tar.gz org.eclipse.papyrus-193b89ef7c445558bd1af39025906ea6743dca77.tar.xz org.eclipse.papyrus-193b89ef7c445558bd1af39025906ea6743dca77.zip | |
Bug 533679: Creation of CFrag should not graphically move elements
Fix the handling of operand ownership for execution specifications
to account for (a) that they are not started/finished only by
ExecutionOccurrenceSpecifications specifically and (b) that they
are not always provided by the rows of the grid model.
Since the updating of the rows and columns and fragment ownership
is so often done in a read-only context (following operation
execution on the history) we can avoid redundant calculations
by just always posting the update asynchronously and throttling
multiple pending calculations.
Altogether this results in the calculation of operand ownership
upon initial creation of a combined fragment not being immediately
overridden by an incorrect calculation that puts all of the
fragments back into the root interaction.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=533679
Change-Id: I2abb81a920e2a8a7f20d3a6b702d3194d8e7ae8e
Signed-off-by: Christian W. Damus <give.a.damus@gmail.com>
Diffstat (limited to 'releng/toolsmiths/targetPlatform/eclipse/org.eclipse.papyrus.toolsmiths.eclipse.targetplatform.target')
0 files changed, 0 insertions, 0 deletions