Home page: Hints: add a Hide/Show function, add a limit by parent function,
These hints mushroom into unmanageable volumes. It should be possible to show smaller and/or only specific groups. I have to page through the whole massive list to pick out the few of interest
- Hide/Show: often I only want to view the ancestors/descendants for a specific lineage. Could be: biological parents, biological father, stepfather, adoptive mother
- Could at least be able to choose Hide/Show individual by individual
Comments
-
If a tool is proving unmanagable for you, perhaps you need to try a different tool? I suggest the chart/tree views. For a person's ancestors, use the fan chart, set to Research Helps.
For a person's descendants, use the descendancy chart, with Record Hints turned on.
Either way, just look for blue. If you open the profile in a new tab, then you can research its hints with all of the person's details and immediate family right there, rather than poking around in the dark (like the Hints list on the homepage feels like, to me).
2 -
Ok,,,,, I found it finally… pull up my family tree and then choose the fan display…. Unfortunately this only shows the “backbone”, only parents, grandparents, great grandparents…. the hints cover extended relationships….. siblings, cousins, step/adoptive… etc…
0 -
For step or adoptive parents, the fan chart responds to the "preferred" setting, same as the two pedigree views. For siblings and cousins, you need the other direction: choose an ancestor and switch to the descendancy view. As a bonus, it can show all of a descendant's spouses, so you don't need to fiddle with "preferred" settings.
0 -
This is pretty labor intensive. I am looking for a sort algorithm that takes all the hints and allows me to select which lineage to view. Since all the hints already show what lineage connects me to each individual it should be a fairly direct programming problem.
Manually going in and developing multiple trees to look at is too much complication, too much effort.
I appreciate your innovative approach, quite unique.
1 -
@JLEd17 As has often been discussed here in the Community, asking the site to do the computations, with 8 billion names in the tree, and who knows how many more billions of records, would bring the site crashing to a halt. It would not speed up your workflow.
1
