Skip to main content
diff options
authorChristian W. Damus2018-05-08 10:42:26 -0400
committerNicolas FAUVERGUE2018-06-05 05:31:15 -0400
commit193b89ef7c445558bd1af39025906ea6743dca77 (patch)
treebe1238bece6665363fb2660b2ce282dd27a92775 /
parent9ff5fff7785695f43ee84facab4ae4f02800bb6f (diff)
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. Change-Id: I2abb81a920e2a8a7f20d3a6b702d3194d8e7ae8e Signed-off-by: Christian W. Damus <>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions

Back to the top