Bug 485390 - Bad display with compartment
Summary: Bad display with compartment
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Diagram (show other bugs)
Version: 3.1.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-01-08 03:45 EST by Esteban DUGUEPEROUX CLA
Modified: 2016-01-12 03:49 EST (History)
2 users (show)

See Also:

Attachments
Sample project to reproduce (177.52 KB, application/zip)
2016-01-08 03:45 EST, Esteban DUGUEPEROUX CLA 		no flags Details
Image of the bad display (17.62 KB, image/jpeg)
2016-01-08 03:47 EST, Esteban DUGUEPEROUX 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 Esteban DUGUEPEROUX CLA 2016-01-08 03:45:53 EST 
Created attachment 259065 [details]
Sample project to reproduce

Using the attached project I get a bad display on compartment, see attached image.

Scenario to reproduce :

1. Import the projects from attached archive
2. Launch a runtime
3. Import AQLBug.test in this second runtime
4. Open diagram and see the bad display
Comment 1 Esteban DUGUEPEROUX CLA 2016-01-08 03:47:32 EST 
Created attachment 259066 [details]
Image of the bad display
Comment 2 Esteban DUGUEPEROUX CLA 2016-01-08 03:49:08 EST 
The bad display seems due to the use of "Height/Width Compu... Expression" different of -1
Comment 3 Laurent Fasani CLA 2016-01-11 04:51:07 EST 
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.
Comment 4 Maxime Porhel CLA 2016-01-12 03:49:10 EST 
We should document and put warning message for this: 
 . -1 is mandatory as size of the region container in the direction of the stack of regions. 
 . the other dimension is free but should be -1 to let the RegionContainer size be managed by the region sizes. 
 . all the region mappings should have the same default width for vStack and height for hStack. 

Note that the auto-size action seems to behave differently for containers, RegionContainers and region regarding the default size entered on the VSM.