Fixed!
Okay. I now see this.
Having both checked adds potential overlapping lines and multiples of the same sets of parents and parent’s other families which does get messy.
1 Like
I’ve implemented more example badges. They are available in the latest version (v0.1.46).
The filter result badge will be the most interesting for most users. You can use the Filter Gramplet in the sidebar and the matching results in the tree will be highlighted with a badge.
Below you can see an example where the filter searches for all people with “Garner” in their name and the matching people in the tree have a blue bullseye badge.
Hope this is useful for some of you!
2 Likes
The
Not that it’s important but having updated a few mins ago, the version I got was 0.1.47
That’s correct. I’ve created a new version that includes a fix/improvement for badge callbacks. I don’t want to spam this thread with every minor update, so there may be newer versions that I haven’t introduced here.
2 Likes
Is that on your to-do list? It would make it possible to fit many more people on a printed page or poster.
It is, but it’s not the highest priority. Depending on how much time I have to work on this addon and how fast I solve the remaining problems, I’ll probably look at it in a week or two. We will see…
I’ll definitely announce it here in this thread once it’s implemented.
1 Like
Could you add a “Reset” for the view configuration that deletes the .gramps/gramps52/Ancestry_family_tree_view.ini or resets the values to defaults and applies those values?
I’ve tweaked the configuration and then wondered if the View rendering flaws were because of my tweaks. And there are too many settings to remember the defaults.
And a Help button that opens the .gpr.py attribute for the help_url in the configuration would be welcome. Which, during the beta, should be https://github.com/ztlxltl/FamilyTreeView/blob/main/README.md. As it nears release (after the name for the addon has been finalized), a wiki page will be created and the help_url can point there.
register(GENERAL,
id = "family_tree_view_example_badges",
name = _("FamilyTreeView Example Badges"),
description = _("Example badges for FamilyTreeView."),
category = "family_tree_view_badge_addon",
version = '0.1.47',
gramps_target_version = "5.2",
status = BETA,
fname = "family_tree_view_example_badges.py",
authors = ["ztlxltl"],
authors_email = ["ztlxltl@gmx.net"],
# depends_on = ["familytreeview"],
help_url = "https://github.com/ztlxltl/FamilyTreeView/blob/main/README.md",
load_on_reg = True,
)
Without a help button (or an in-View help icon, such as with the Life Line addons), the help_url can be accessed via the Wiki button for the addon’s listing in the Addon Manager or Plugin Manager. The Timeline Pedigree View addon Charts view mode has a context menu with an About Timeline Pedigree View
1 Like
@emyoulation
Both ideas are reasonable. I’ll add them to my list.
Regarding resetting the addon’s configuration, I have a feeling that this could be a feature of Gramps itself, for example a Reset button for each addon in the addon manager next to the install button. That way it’s available for all addons, and the user would find it in a single location rather than having to search for it.
1 Like
The FamilyTreeView addon (like several Charts views) supports the mouse scroll wheel. But only for zoom. Unfortunately, there are no standards for modifiers and mouse button actions in Gramps charts.
FamilyTreeView addon
| modifier | Left | Center | Wheel | Right |
|---|---|---|---|---|
| none | show details |
show details |
zoom in/out |
no action |
| Shift | modifier ignored |
modifier ignored |
modifier ignored |
no action |
| Ctrl | modifier ignored |
modifier ignored |
modifier ignored |
no action |
| Alt | modifier ignored |
modifier ignored |
modifier ignored |
no action |
| press and drag |
✥ | ✥ | ✥ | no action |
Suggested actions
| modifier | Left | Center | Wheel | Right |
|---|---|---|---|---|
| none | show details |
show details |
scroll |
context menu |
| Shift | modifier ignored |
modifier ignored |
scroll ↔️ |
no action |
| Ctrl | modifier ignored |
modifier ignored |
zoom ± |
no action |
| Alt | modifier ignored |
reset zoom re-center |
reset zoom re-center |
no action |
| press and drag |
✥ | zoom marquee |
zoom marquee |
no action |
The Timeline Pedigree View addon Charts view mode has a Shift Scrollwheel modifier to shift from horizontal to vertical scrolling. It chooses a somewhat counter-intuitive behavior. Since the progression of data is horizontal, the developer choose to make the unmodified scroll also horizontal. And oddly for a language read left-to-right, the upwards wheel roll scrolls leftwards… reverse of what would naturally follow. That’s more appropriate for languages read right-to-left. The shift modified wheel roll scrolls vertically. And, as expected, roll upwards will scroll upwards.
1 Like
Could the font placement issue be related to changes in font size/family using the Themes addon for Preferences?
1 Like
I use the standard font provided by my ubuntu 22.04
Same problem without the Theme addon.
2 Likes
Thanks for your suggestion! I can definitely include those two alternatives. I (and probably most users) know both from navigating a document (e.g. pdf, website etc., your suggestion) and from navigating a map (e.g. OpenStreetMap, Google Maps, etc., current implementation). Before I developed FTV, I used GraphView, so I was used to the “map-style” navigation, so I implemented it that way. For people coming from the other chart views that work with “document-style” navigation, your suggestion may be more intuitive.
1 Like
I had a private conversation with @SNoiraud about this issue. His defaults on Ubuntu 22.04.5 LTS are “Sans 13”. I have the same OS and my defaults are “Ubuntu 11” (the default font of the Ubuntu OS is also called “Ubuntu”). When I select the font “Sans Regular” (which is shown as “Sans” in the preferences) on my machine and I select font size 13, the result looks different from his “Sans 13”, not so much cut off and the marriage date is inside the box. So I’m out of ideas on this one.
1 Like
I just released a new version of FTV (v0.1.48) that adds siblings expanders to the tree. As with the other expanders, you can hide them or make them expand automatically in the config window.
With these new expanders, you can visualize the active person’s aunts/uncles, first cousins, great aunts/uncles, great-great aunts/uncles, etc.
The code to build the tree became very complex to be able to deal with the correct placement of all the different cases. So this update took a while. After testing and debugging throughout the week, the code finally reached a state where I couldn’t find any more visualization problems.
The tree builder code is far from perfect, and it seems to be a bit slower than before (I measured about 8% increase in time), but it should be a bit easier to maintain now. There are still a few improvements I plan to make regarding the expanders (and performance), but I think I will look at other to-dos next.
6 Likes
The latest version is so great. I’ve never seen the whole family like this before.
It would be good if the main line of ancestors could be shown in a different color or strength. Because the tree can be very complex. That would give you a bit more orientation.
2 Likes
The following was with the version downloaded Thursday. I really, REALLY appreciate the clean output of your work. (Although hairline borders for the Nodes and/or thinner line connectors might print more elegantly. And lower saturation backgrounds would save ink.)
I used the FTV to identify which cousins (though a paternal great-aunt) had Thumbnails. After painstakingly collapsing and expanding a subset of branches, I attempted to generate a PDF via Print to File. As soon as the Print dialog appeared, all the expanders reverted to default states. So that subset could not Printed.
An earlier attempt to isolate a subsection via Filters. But in FTV, that just adds a badge to the filter matches. (So I would have to explain the “matches filter” badge when sharing an illustration with distant cousin genealogists.)
Some of the other charts (like the Fan Chart) cut the color saturation of the non-matches. Given the spectrums of color, that’s somewhat hard to discern. (I hacked the Fan chart view to drop the non matches to grayscale. This lets me filter to print common ancestry Fans charts for myself and another distant cousin to illustrate pedigree collapse and double cousin heritage.)
Could you have an option either hide the Persons for filter non-match or drop the color saturation to zero for them? Maybe that will be printable if the GUI expanders have to reset.
2 Likes
Your frequent positive feedback is really motivating!
That’s a great idea. I’ll add it to my list.
3 Likes
Amazing addition, many thanks!
1 Like
@emyoulation
Thank you!
I can make this customizable. Added this to my list.
Do you mean the background of the boxes/nodes? This color is taken from the Gramps color scheme, which you can customize in the preferences.
This is very unfortunate. I think it happens because the tree is updated every time the theme is updated (e.g. switching to a dark theme), and the theme is updated when the window is no longer in the foreground (e.g. some text becomes a bit gray). I can look into how to detect an actual theme change with the theme addon or remove the theme change triggered update altogether.
True, that was just a first attempt to test how the communication with the filter gramplet works.
I had this in mind as well. This should be easy to add. I’ll take a look.
That would be very difficult, as some people are necessary to reach others. Dropping something in the middle would be weird, and dropping whole parts of the tree just because a person near the active person doesn’t match the filter is also not intuitive (e.g. hiding all paternal ancestors because the active person’s father doesn’t match the filter).
I’ll try the saturation drop. That should be easy to do.
1 Like
Truly astonishing.
What a new level of clarity is shown us with this work.
Words almost fail me!
Thank you for this.
brian
3 Likes