Update packMode information

diff --git a/doc/info/attrs.html b/doc/info/attrs.html
index 65e7ea09f9cb2a5958bbec8fc2c3df7b167d40ef..4253657a91575eac6b9cc5163cbf2267a34619ca 100644 (file)
--- a/doc/info/attrs.html
+++ b/doc/info/attrs.html
@@ -1232,7 +1232,7 @@ This field indicates which graph component uses the attribute.
 <DT><A NAME=d:pack HREF=#a:pack><STRONG>pack</STRONG></A>
 <DD>  This is true if the value of pack is "true" (case-insensitive) or a
   non-negative integer. If true, each connected component of the graph is
-  laid out separately, and then the graphs are packed tightly.
+  laid out separately, and then the graphs are packed together.
   If pack has an integral value, this is used as the size,
   in <A HREF=#points>points</A>, of
   a margin around each part; otherwise, a default margin of 8 is used.
@@ -1244,7 +1244,7 @@ This field indicates which graph component uses the attribute.
   attribute is just used to set the margin.
 
 <DT><A NAME=d:packmode HREF=#a:packmode><STRONG>packmode</STRONG></A>
-<DD>  This indicates the granularity and method used for packing
+<DD>  This indicates how connected components should be packed
   (cf. <A HREF=#k:packMode>packMode</A>). Note that defining
   <B>packmode</B> will automatically turn on packing as though one had
   set <B>pack=true</B>.
@@ -1851,10 +1851,13 @@ the given types.
   "edgesfirst".
 
 <DT><A NAME=k:packMode><STRONG>packMode</STRONG></A>
-<DD>"node","clust","graph"
-  These specify the granularity of packing connected components when
-  the <A HREF=#d:pack>pack</A> attribute is true. A value of "node" causes
-  packing at the node and edge label, with no overlapping of these objects.
+<DD>"node", "clust" , "graph" , "array{_flags][%d]"
+  <P>
+  The modes "node", "clust" or "graph"
+  specify that the components should be packed together tightly, using
+  the specified granularity.
+  A value of "node" causes
+  packing at the node and edge level, with no overlapping of these objects.
   This produces a layout with the least area, but it also allows interleaving,
   where a node of one component may lie between two nodes in another
   component. A value of "graph" does a packing using the bounding box of the
@@ -1864,6 +1867,18 @@ the given types.
   What effect a value has also depends on the layout algorithm. For
   example, neato does not support clusters, so a value of "clust" will
   have the same effect as the default "node" value.
+  <P>
+  The mode "array{_flags][%d]"
+  indicates that the components should be packed at the 
+  graph level into an array of graphs. By default, the components
+  are in row-major order, with the number of columns roughly the
+  square root of the number of components. If the optional flags
+  contains "c", then column-major order is used. Finally, if the
+  optional integer suffix is used, this specifies the number of 
+  columns for row-major or the number of rows for column-major.
+  Thus, the mode "array_c4" indicates array packing, with 4 rows,
+  starting in the upper left and going down the first column, then
+  down the second column, etc., until all components are used.
 
 <DT><A NAME=k:pagedir><STRONG>pagedir</STRONG></A>
 <DD>"BL", "BR", "TL", "TR", "RB", "RT", "LB", "LT".

diff --git a/doc/infosrc/attrs b/doc/infosrc/attrs
index 812e569a064261362249b438c45502adb47c36af..ff8746f4123c263da2670e1137b59b004271bdce 100644 (file)
--- a/doc/infosrc/attrs
+++ b/doc/infosrc/attrs
@@ -717,7 +717,7 @@ If <TT>overlap_scaling</TT> is positive, the layout is scaled by
 :pack:G:bool/int:false; notdot
 This is true if the value of pack is "true" (case-insensitive) or a
 non-negative integer. If true, each connected component of the graph is
-laid out separately, and then the graphs are packed tightly.
+laid out separately, and then the graphs are packed together.
 If pack has an integral value, this is used as the size,
 in <A HREF=#points>points</A>, of
 a margin around each part; otherwise, a default margin of 8 is used.
@@ -728,7 +728,7 @@ The granularity and method of packing is influenced by the
 For layouts which always do packing, such a twopi, the <B>pack</B>
 attribute is just used to set the margin.
 :packmode:G:packMode:node; notdot
-This indicates the granularity and method used for packing
+This indicates how connected components should be packed
 (cf. <A HREF=#k:packMode>packMode</A>). Note that defining
 <B>packmode</B> will automatically turn on packing as though one had
 set <B>pack=true</B>.

diff --git a/doc/infosrc/types b/doc/infosrc/types
index 98880ec6b64b543b6e57192eadaf438033253ac0..0d773bfd4bb7d4993817090bf93d888cd6813f3f 100644 (file)
--- a/doc/infosrc/types
+++ b/doc/infosrc/types
@@ -159,10 +159,13 @@ reasons, it may be desirable that all edges appear beneath nodes, even
 if the resulting drawing is ambiguous. This can be achieved by choosing
 "edgesfirst".
 :packMode
-"node","clust","graph"
-These specify the granularity of packing connected components when
-the <A HREF=#d:pack>pack</A> attribute is true. A value of "node" causes
-packing at the node and edge label, with no overlapping of these objects.
+"node", "clust" , "graph" , "array{_flags][%d]"
+<P>
+The modes "node", "clust" or "graph"
+specify that the components should be packed together tightly, using
+the specified granularity.
+A value of "node" causes
+packing at the node and edge level, with no overlapping of these objects.
 This produces a layout with the least area, but it also allows interleaving,
 where a node of one component may lie between two nodes in another
 component. A value of "graph" does a packing using the bounding box of the
@@ -172,6 +175,18 @@ A value of "clust" guarantees that top-level clusters are kept intact.
 What effect a value has also depends on the layout algorithm. For
 example, neato does not support clusters, so a value of "clust" will
 have the same effect as the default "node" value.
+<P>
+The mode "array{_flags][%d]"
+indicates that the components should be packed at the 
+graph level into an array of graphs. By default, the components
+are in row-major order, with the number of columns roughly the
+square root of the number of components. If the optional flags
+contains "c", then column-major order is used. Finally, if the
+optional integer suffix is used, this specifies the number of 
+columns for row-major or the number of rows for column-major.
+Thus, the mode "array_c4" indicates array packing, with 4 rows,
+starting in the upper left and going down the first column, then
+down the second column, etc., until all components are used.
 :pagedir
 "BL", "BR", "TL", "TR", "RB", "RT", "LB", "LT".
 These specify the 8 row or column major orders for traversing a