GEDCOM Navigator: eldre versjoner og versjonshistorikk

Full Changelog: v1.10.0...v1.11.0

What's New in v1.9.19
DNA Match Detection for Non-Ancestry GEDCOM Files
GEDCOM Navigator now finds DNA matches in family trees exported from any genealogy software, not just Ancestry.
Previously, DNA-match detection relied on Ancestry-specific data structures (_MTTAG custom tags and AncestryDNA Match source citations). Files exported from other programs — MyHeritage, Family Historian, Legacy Family Tree, RootsMagic, and others — were not recognized.
When your GEDCOM file was not exported by Ancestry, the app now scans the custom fields those programs use to record DNA relationships:
- Custom events and facts (EVEN/FACT records with a DNA-related TYPE, e.g. "DNA Match" or "MyHeritage DNA")
- Family Historian custom attributes (_ATTR)
- Reference number fields (REFN)
- Custom _DNA-style tags
The match keyword is configurable (default: "DNA"). When a custom event uses the generic TYPE value "Custom", the app uses the event's own text as the label — so a record like 1 FACT MyHeritage DNA / 2 TYPE Custom appears and matches as "MyHeritage DNA".
Notes (free-text NOTE fields) are excluded by default — they mention "DNA" too often to be useful for detection. You can enable note scanning with the new Scan note text for matches toggle in Preferences.
New controls
- Select Tag browser — for non-Ancestry files, the tag browser now shows a catalog of the custom field types discovered in your GEDCOM. Columns are sortable by clicking any header, so you can quickly find and select the specific tag to match on.
Preferences: Scan note text for matches — opt in to include free-text NOTE fields in DNA detection.
- CLI: --detection-fields — controls which field categories are scanned (events/facts, custom attributes, reference numbers, etc.).
- CLI: --list-tags — now shows the full catalog of discovered custom field types for non-Ancestry files.
Bug Fixes
- Full siblings display with a solid connector inside mixed half-sibling groups — when a sibling group with hidden parents included both full and half-siblings, the entire group's connector bar was drawn in the half-sibling dashed style, making full siblings appear to be half-siblings. Full-sibling groups within the bar now use the solid style; only the bridges between different family groups use the dashed style.
- Half-siblings with hidden parents are placed on their sibling's row — a half-sibling whose own parents are not visible was being placed as a disconnected component far from their sibling group. They are now correctly attached on the same row as their siblings.
Full Changelog: v1.9.18...v1.9.19