Summary

• Page properties (1 modified, 0 added, 0 removed)
• Objects (1 modified, 0 added, 0 removed)
  • Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Content

...	...	@@ -113,19 +113,23 @@
113	113	}
114	114	{{/code}}
115	115
116		-It is not hard to guess what {{code language="none"}}getPriority(){{/code}} does: it returns the priority a given layout configuration has. If two layout configurations set a layout option to different values on a given graph element, the value set by the configuration with lower priority gets overwritten. The other three methods look a bit more obscure, so we have to provide more details on what the options manager does, exactly.
	116	+It is not hard to guess what {{code language="none"}}getPriority(){{/code}} does: it returns the priority a given layout configuration has. If two layout configurations set a layout option to different values on a given graph element, the value set by the configuration with higher priority wins. The other three methods look a bit more obscure, so we have to provide more details on what the options manager does, exactly.
117	117
118	118	ENRICHING (+ WHAT IS A LAYOUT CONTEXT)
119	119
120		-TRANSFERRING
	120	+The {{code language="none"}}transferValues(...){{/code}} method is the main workhorse of the interface. This is where a KGraph element, identified by the given layout context, is equipped with the layout option values a layout configuration deems necessary. It thus becomes the most important part of a layout configuration that you absolutely have to implement, no excuses. If for example every {{code language="none"}}KNode{{/code}} should have its port constraints set to {{code language="none"}}FIXED_POS{{/code}}, this is the place to do it.
121	121
122		-GETVALUE (for the layout view?)
	122	+With all these layout configurations active, it's by no means clear which layout option values KGraph elements will end up with during the layout process. Enter the {{code language="none"}}getValue(...){{/code}} method. For a given element and layout option, it returns the value it would set on the element if {{code language="none"}}transferValues(...){{/code}} was called. This method is mainly used by the Layout view to inform the user about the layout option values of whatever graph element he (or she) has clicked on. It is also the method you can safely neglect to implement if your final product won't include the layout view anyway.
123	123
124	124	== (% style="line-height: 1.4285715;" %)Implementing a Layout Configuration(%%) ==
125	125
126		-(% style="line-height: 1.4285715;" %)deciding what options are applicable depending on the context object; setting the options;
	126	+{{warning title="ToDo"}}
	127	+deciding what options are applicable depending on the context object; setting the options;
	128	+{{/warning}}
127	127
	130	+(% style="line-height: 1.4285715;" %)
128	128
	132	+
129	129	= (% style="line-height: 1.4285715;" %)Programmatically Setting Layout Options(%%) =
130	130
131	131	{{warning title="ToDo"}}

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-7701010
	1	+7701011

URL

...	...	@@ -1,1 +1,1 @@
1		-https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/7701010/Configuring Automatic Layout
	1	+https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/7701011/Configuring Automatic Layout