|
| Re: Saving figures's constraints from layouting in notation model [message #1024447 is a reply to message #1023860] |
Tue, 26 March 2013 07:58   |
 Thomas Beyer
Messages: 55
Registered: February 2013 |
Member |
|
|
Hi Yves,
the notation model knows two stages:
1. width/height explicitely set to a value. The figures will try to layout to this size.
2. default size (-1/-1) which is persistet as a null entry for the layout constraints. The figures will take the preferred size, that they require to fully display their contents. So if child figures (sizes) changes, the parent changes accordingly.
Maybe this already answers your question?
You could also manually set the figures size to -1/-1.
I am not aware of a solution, that would discriminate the source of modification.
There are also other actions, that modify the size of the size automatically to specific values (MakeSameSizeAction for example).
If you want to store this kind of information in the notation model, you would have to extend it and modify all actions and commands, to reflect this modification. This yould get a cumbersome task, because if you check the call-hierarchy for SetBoundsCommand, you will find quiet some consumers, that would need to be adressed.
Regards
Thomas
|
|
|
| Re: Saving figures's constraints from layouting in notation model [message #1024461 is a reply to message #1023860] |
Tue, 26 March 2013 07:58 |
Thomas Beyer
Messages: 93
Registered: July 2009 |
Member |
|
|
Hi Yves,
the notation model knows two stages:
1. width/height explicitely set to a value. The figures will try to layout to this size.
2. default size (-1/-1) which is persistet as a null entry for the layout constraints. The figures will take the preferred size, that they require to fully display their contents. So if child figures (sizes) changes, the parent changes accordingly.
Maybe this already answers your question?
You could also manually set the figures size to -1/-1.
I am not aware of a solution, that would discriminate the source of modification.
There are also other actions, that modify the size of the size automatically to specific values (MakeSameSizeAction for example).
If you want to store this kind of information in the notation model, you would have to extend it and modify all actions and commands, to reflect this modification. This yould get a cumbersome task, because if you check the call-hierarchy for SetBoundsCommand, you will find quiet some consumers, that would need to be adressed.
Regards
Thomas
|
|
|
|
Powered by
FUDForum. Page generated in 0.03622 seconds
] 
Search
Help
Register
Login
Home
