Bug 510683 - [ModelEditor] Sash Editor should takes into account sash position set into di model.
Summary: [ModelEditor] Sash Editor should takes into account sash position set into di...
Status: NEW
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 3.0.0   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-19 07:52 EST by Cedric Dumoulin CLA
Modified: 2017-09-08 11:41 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cedric Dumoulin CLA 2017-01-19 07:52:12 EST
The Sash Editor allows to have multiple views separated by 'sashes'. Actually, the sash is always created in the middle of the two views to separate. 
End user can move the sash, but the new position is not saved in di models, and the sash position that can be set in di models is not taken into account.

The Sash Editor should take into account the sash initial position, and should save the sash position in the model when end user change it.

The di model already have an attribute to set the sash position. This attribute is not carried to the SashModelPart (which is responsible to create SWT SashForm).
To take into account the sash initial position, we need :
 - to carry the sash position value to the SashModelPart
 - let SashModelPart set the sash position with
 
 To save the position after the end user change it, we need to :
  - Detect the position change
  - Let the SashWindowsContainer throw an event when the position change
  - Let the di model listen to such event, and save the new position.
Comment 1 Cedric Dumoulin CLA 2017-01-19 16:16:11 EST
Branch is created :
origin/committers/cdumoulin/bugs/510683-Sash_Editor

The sash initial position is now taken into account :
commit 53c40b9ca08a62c0790879dde3e42351ab479e44