Bug 497055 - Change computation size expressions of a regions container in the VSM can caused problems
Summary: Change computation size expressions of a regions container in the VSM can cau...
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Diagram (show other bugs)
Version: 4.0.0   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-06-30 04:12 EDT by Laurent Redor CLA
Modified: 2016-06-30 11:15 EDT (History)
1 user (show)

See Also:

Attachments
CompartmentsChangeComputationExpressionLayoutProblem.zip (4.84 KB, application/x-zip-compressed)
2016-06-30 04:12 EDT, Laurent Redor CLA 		no flags Details
View All 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 Laurent Redor CLA 2016-06-30 04:12:44 EDT 
Created attachment 262808 [details]
CompartmentsChangeComputationExpressionLayoutProblem.zip

If the "Width Computation Expression" or the "Height Computation Expression" of a regions container is changed in the VSM, the regions containers, of existing representations, are resized but not their regions. The regions have a wrong size.

Steps to reproduce:
* Import the project "Compartments" from "CompartmentsChangeComputationExpressionLayoutProblem.zip"
* Open the diagram "HStackDiag"
* Launch "Open Definition" with contextual menu on "p1"
* On the Gradient style of "HStack" mapping, in the Advanced tab of the properties view, replace 5 by 10 for Height and Width Computation Expressions.
* Go to the "HStackDiag" diagram: The container p1 is resized but not its region: KO.

This bug has a minor priority because:
* as said in documentation, -1 is recommanderd for regions container for Height and Width Computation Expressions
* this is not a main scenario
Comment 1 Laurent Fasani CLA 2016-06-30 11:15:32 EDT 
Thanks for your detailed bug report.
We have reproduced this issue and we consider it as valid.
Nevertheless, we have currently not planned to work on it in the following releases.