That is not correct. In line 42 there is SEX X. That is no valid GEDCOM 5.5.1. It is GEDCOM 7 or GEDCOM-L and that is the reason that this is indicated in the header.
The empty line at the end of the file is an error, I will delete it.
The reason to set up that file was a discussion in CompGen Discourse about how to visualize a complex family tree. A small tree, that contains implex, adoptive family, same sex partners, and diverse sex of a person.
This resonated with me because I have a fair number of multiple marriages in my tree. So I wrote a patch to provide the spouse’s name for myself. If nobody else is working on this, should I submit my patch as a pull request to the FamilyTreeView repository? @ztlxltl That would remove an item from your TODO list, and let you keep your focus on the many important issues.
@TJB Are you TJBFTV on GitHub?
I saw your other PR. For the timeline (which is what all your PRs are for, according to your comment on GitHub), I only have one feature that I’ve partially implemented. So you can open those PRs, and I will probably review and merge many of them soon. If you have PRs for other parts of the code, it may take longer for me to merge them, as I want to finish a few partially implemented / not fully debugged features first.
I want to give a small update on what has happened between the last version I talked about in this thread (v0.1.52) and the latest version of FTV (v0.1.62) so that everyone is aware of the new features:
The tree doesn’t rebuild twice in a row in certain situations (e.g. when the active person changes). This should have improved the performance slightly in those situations.
There is a new option to change the image resolution from normal to large or original. This way the high-resolution images will not become pixelated when you zoom in. Here is an example of a high resolution image of example tree:
I’ve also improved the implementation of images and icons, including caching renderings (pixbufs) of svg icons to improve performance. This now allows icons to be used in custom badges. Also, the Rsvg requirement for FTV could be dropped due to the cleanup.
Printing/exporting the visualization: I added a new option to scale the tree down to the size of a page. Unfortunately this can lead to distorted or empty output on Windows. I also implemented a direct SVG export that seems to work on all platforms. The features are discussed in more detail in this thread. The new export icon next to the print icon:
Unfortunately, the export icon is not available on Windows.
When editing a person or family, the tree position doesn’t reset to the active person anymore.
A better close icon for the pannel is used, which is available on Windows.
18499: ERROR: grampsapp.py: line 188: Unhandled exception
Traceback (most recent call last):
File "/home/districtsupport/.local/lib/python3.11/site-packages/gramps/gui/viewmanager.py", line 968, in view_changed
self.__change_page(page_num)
File "/home/districtsupport/.local/lib/python3.11/site-packages/gramps/gui/viewmanager.py", line 984, in __change_page
self.active_page.set_active()
File "/home/districtsupport/.local/lib/python3.11/site-packages/gramps/gui/views/navigationview.py", line 159, in set_active
self.goto_active(None)
File "/home/districtsupport/.local/lib/python3.11/site-packages/gramps/gui/views/navigationview.py", line 194, in goto_active
self.goto_handle(active_handle)
File "/home/districtsupport/.gramps/gramps52/plugins/family_tree_view.py", line 325, in goto_handle
self.rebuild_tree()
File "/home/districtsupport/.gramps/gramps52/plugins/family_tree_view.py", line 361, in rebuild_tree
self.widget_manager.tree_builder.process_person(root_person_handle, 0, 0, ahnentafel=1)
File "/home/districtsupport/.gramps/gramps52/plugins/family_tree_view_tree_builder.py", line 137, in process_person
person_bounds = self.process_families(person_handle, person_bounds, x_person, person_generation, dry_run, process_descendants, skip_family_handle=skip_family_handle, child_handle_with_other_parents_to_collapse=child_handle_with_other_parents_to_collapse)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/districtsupport/.gramps/gramps52/plugins/family_tree_view_tree_builder.py", line 234, in process_families
family_bounds = self.widget_manager.add_family(family_handle, x_family, person_generation)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/districtsupport/.gramps/gramps52/plugins/family_tree_view_widget_manager.py", line 325, in add_family
family_bounds = self.canvas_manager.add_family(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/districtsupport/.gramps/gramps52/plugins/family_tree_view_canvas_manager.py", line 349, in add_family
self.add_badges(badges, x+self.family_width/2-self.padding, y)
File "/home/districtsupport/.gramps/gramps52/plugins/family_tree_view_canvas_manager.py", line 504, in add_badges
self.add_from_image_spec(
File "/home/districtsupport/.gramps/gramps52/plugins/family_tree_view_canvas_manager.py", line 598, in add_from_image_spec
with open(path, 'r') as file:
^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '/home/districtsupport/.gramps/gramps52/plugins/src/icons/descendants.svg'
Look at the ‘Life Line Descendant Chart’ and the ‘Life Line Ancestor Chart’. The Windows version of both of those Charts have an icon for the export as SVG option:
Yes, as you can see in that screen shot, the hover over says 'Save the Life Line Chart view but the dialog that appear when you click that icon is titled ‘Export View as SVG’.
Could you use that icon in place of the one you are using at the moment?
@emyoulation
This looks like something is wrong with your path to FTV. There should be a FamilyTreeView/ after /home/districtsupport/.gramps/gramps52/plugins/.
This thread was started in Dec 2024 and already has 332 postings with an estimated 78 minute read time. Splitting at the FTV 0.1.65 announcement on 15 Feb 2024.
In consultation with @emyoulation, this thread has been split at the v0.1.65 anouncement of the FamilyTreeView addon due to the thread’s length (>330 comments). The discussion can be continued in this new thread.