Est-ce que quelqu’un peut reproduire ce problème avec le rapport graphique Arbre des descendants... et ces options?
Can someone reproduce this issue with Graphical Descendant Chart report and these options?
Thank you so much, Jérôme, that’s very kind of you!!!
Another question: Do you sometimes see responses in English, or is the entire discussion thread in French?
I see your last message in English…
…that was the plan! In fact, English-speaking readers can read the French in this thread via automatic translation. The reverse doesn’t work. This explains why responses in English may sometimes confuse French speakers (‘‘well, not Canadians’’)—only those who know only “Brian is in the kitchen”… (good luck to the automatic translator!)
I don’t see clearly how to enter a title for this report. Based on your error message, the issue is related to title handling.
Very strange, no matter what I put for the title—“do not include a title” or any other option—I still get an error message.
Actually, by “title,” I think it refers more to a simple variable name in the code (title) used to generate the report and determine whether to use one or multiple pages.
There is a connection with the tree size, output format, and output dimensions. Changing the report name won’t make much difference. In fact, I retained all your options (including the choice of name) during testing to reproduce the error.
list_title and self.__pages[0, 0] appear to simply point to the first page. Do you encounter this issue with formats other than SVG?
I do have an idea for experimenting with a fix, but it doesn’t make sense if I can’t reproduce the problem.
else:
self.title.width = self.doc.get_usable_width()
- self.__pages[0, 0].add_box(self.title)
+ self.__pages[x_page, 0].add_box(self.title)
I indeed have the same issue in PDF format.
But the other types of trees work.
A corner case!
Looking at the history of this part of the code, it turns out this dates back to January 7, 2011!
Do you have, in this tree, individuals with more than 2 spouses (3, 4, 5, etc.)?
Coming late into this thread, please excuse me.
Are you looking for something like this:
I create many such “Family Lines” graph reports, limiting the number of generations or individuals so that the global picture can be understood at first glance. The raw graph is processed by a custom script to add an HTML image map over the graph, extracting hyperlink information to create links to person and family pages. The resulting file is inserted into a NarrativeWeb directory.
Notice that marriage dates are present. This is a standard option in Family Lines.
The boxes are clickable to jump to the ad hoc page.
The family Lines generator has been modified to display colour borders showing the status of my data (new, partial, complete, lapse = lack of documents due to loss or destruction, restriction = access to archive is restricted by law, no posterity, …). Thus I visually know on which branch I must put some effort.
1 Like
Has a suitable tree or wheel graphical view been found?
Hello, the relational diagram with the options you indicated is the best option for me, thank you again for your advice! I understand that it is not possible to delete the Marriage nodes, or at least the marriage date (since it’s either all dates or none).
Thank you again!
It indeed appears that the “family node” (which sometimes contains the marriage date) is necessary for the code. One might perhaps tinker “on the margins,” but this object is essential to establish the parent<->child link within a single-parent or non-single-parent family.