We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
My grandmother was widowed, then re-married.
Both of her husbands render to her right.
This makes for a convoluted graph with lines jumping over each other. Like this:
+------------------------------------+ | | grandma ------- husband1 husband2
When you add the children from each marriage, it gets very confusing very fast.
Would suggest a flag that chooses whether to render a node to the left, or to the right.
That is, "Put husband1 to the left of grandma, and put husband2 to the right of grandma".
Like so:
husband1 ------ grandma ------- husband2
This would go a long way towards untangling some/many family trees.
The flag should. be optional so it doesn't break existing json files.
If someone marries three times the problem reappears but the above feature would satisfy most cases
The text was updated successfully, but these errors were encountered:
No branches or pull requests
My grandmother was widowed, then re-married.
Both of her husbands render to her right.
This makes for a convoluted graph with lines jumping over each other. Like this:
When you add the children from each marriage, it gets very confusing very fast.
Would suggest a flag that chooses whether to render a node to the left, or to the right.
That is, "Put husband1 to the left of grandma, and put husband2 to the right of grandma".
Like so:
This would go a long way towards untangling some/many family trees.
The flag should. be optional so it doesn't break existing json files.
If someone marries three times the problem reappears but the above feature would satisfy most cases
The text was updated successfully, but these errors were encountered: