There is no reason why the textual_flow class needs to derive its connectivity value from XML input or the genealogical cache; users should be able to specify different connectivity limits anytime they invoke the print_textual_flow script. To accommodate default connectivity limits for different units and to ensure backwards compatibility, connectivity values should still be permitted in the input XML, but print_textual_flow should also have an optional -k parameter for setting the connectivity limit at runtime.
Since I'll be working in the textual_flow class for #5, I might as well add this feature while I'm at it.
There is no reason why the
textual_flowclass needs to derive its connectivity value from XML input or the genealogical cache; users should be able to specify different connectivity limits anytime they invoke theprint_textual_flowscript. To accommodate default connectivity limits for different units and to ensure backwards compatibility, connectivity values should still be permitted in the input XML, butprint_textual_flowshould also have an optional-kparameter for setting the connectivity limit at runtime.Since I'll be working in the
textual_flowclass for #5, I might as well add this feature while I'm at it.