Decendency Chart numbering overwrites

[Douglas Terry]

I have been working on a fairly deep family tree and noticed with I chose the decendency chart that it doesn't take more than 5 levels deep before the numbering scheme starts overwriting the family element box. This is independant of whether the details are shown or not and seems to be related to a fixed table column width without wrapping. Is there any way to avoid this?

[Gerry Kroll]

The only way to overcome this is to modify the column width definitions in the relevant theme.

Good luck.

[Douglas Terry]

Would it make sense that there be a minimum width (ie like currently) to cover up to 3 generations deep and then based on the additional generations depth chosen that this number be extended. This sounds like a better programatic solution. If you want I can prototype something and let you know what works.

[Gerry Kroll]

I think this is too much trouble, for very little benefit.

[Douglas Terry]

Thanks. I went looking through the code and there seems to already be some code to handle this case. In ./includes/functions/functions_chart.php in the "function print_sosa_number(..)" about 10 lines from the start of that function there is already a test for $wideSosa, that changes the default width of this Sosa column from 15 to 50. If I set the value to 100 it covers to about 7 levels deep which is generally big enough. I have at least made this a change in my version and if it doesn't make it into the SVN then I will look at a manual change each time I update my version.

if (isset($wideSosa) && $wideSosa) $sosaWidth = 100;        // If specified, allow more room (was 50)

[Gerry Kroll]

This COULD be made a GEDCOM configuration option, .... which section??

The width should be selectable: 25, 50, 75, 100, 125, 150 . default 50.

[Douglas Terry]

I am not sure that it is acting as a GEDCOM configurable option because for some reason in ./dependency.php in the wideSosa variable is set to true around line 147. I am having difficulty right now searching all the source for where else the variable may be updated. If it was selectable that would be great but the ./includes/functions/functions_chart.php needs to be updated to support the selected GEDCOM value.

[Gerry Kroll]

This would have to be a new option in the GEDCOM configuration.

Once implemented, the main program code can easily be amended to use this new GEDCOM configuration setting in place of what's currently hard-coded.

This isn't hard to do. The main question is where in the GEDCOM configuration this new option should appear.

[Gerry Kroll]

Douglas:
Try the attached. There are new GEDCOM configuration options in the Display, Layout, and Reports group, Layout section.

You can select fixed widths for the SOSA numbers. If you select "Variable", the SOSA numbers will take as much space as they need, and the rest of the chart will be positioned accordingly.

"Variable" has always been there, but wasn't documented. Specifying blank in the function_charts code you previously identified has always done this.

The new configuration options just make all this more accessible.

Please let me know how this works for you. This stuff isn't in the SVN yet. Have to do a bunch of translations first.

[Douglas Terry]

Gerry this is brilliant work. I tried all the values and they worked as expected. It is great to see the variable which is probably what will be used most of the time for me as it grows or shrinks as needed.

As a thankyou here is an Email List report that I created that you may find useful. It will generate a list of all family tree elements whos users aren't dead (ie have a death date associated). I use it to then send out emailings to people so that they can clarify facts.