Community
Participate
Working Groups
When resize constraint is set to NONE for a node it should not be possible to resize it on diagram for example; see Port node in TaiPan.
This scr blocks #114061 that states (among other things): > Note, resize constraints are not yet taken from gmfgraph > (gmfgraph.Node#resizeConstraints).
Created attachment 37857 [details] Fixes the subj Please note that taipan sample should be recreated (the both recreation of the taipan.gmfgen and regeneration of the editor code is required). Unfortunately, I can not produce this myself, because there is some other waiting patches for taipan which is not yet committed.
Created attachment 37944 [details] Fixes the subj + tests + Direction.ALL as default direction constraint This extends previous patch with tests and new functionality, which is implictly required. It allows nodes to be fully resizable by introducing new Direction.ALL into the gmfgraph model. The default value for gmfgraph.Node#direction is now set to ALL to confrom to the previous behavior.
Refactored and committed. Patch includes "not_implemented_scr_129362_testViewmapRequiredPluginIDs" which doesn't compile, thus was thrown away. The bugzilla remains open to resolve next issue: gmfgraph.Node#resizeConstraint was intended to hold *constraint*, or *limitation* of resize operation, not resize *allowance* as it's implemented in the proposed patch. IOW, resizeConstraint == NONE means 'resize whatever you like", and "VERTICAL" means 'resize only in horizontal directions'. We should either change DirectionMapper (as a side note, we may wish to change the name as well ;) and default value of resizeConstraints to NONE instead of ALL, or to rename graphdef.Node#resizeConstraint to smth like resizeDirections.
Milestone updated.
In draw2d these constants are used to provide allowance so inverting their meaning in our model will lead to confusion. And it's more convenient to think about what we add rather than what we subtract since it's may be not obvious what we subtract from )))
-
[target cleanup] 1.0 RC was the original target milestone for this bug
[GMF Restructure] Bug 319140 : product GMF and component Generation was the original product and component for this bug