@roptat
I updated the addon to only distinguish between primary and all events if it makes a difference for the person in the panel. In the config window, all options are visible because they apply to all persons including those where the distinction makes sense.
The alternative lines under the Experimental tab are much better. Not so long anymore. Maybe you could spread the distance between the horizontal lines a little further. Otherwise you get lost in all the lines.
Now you just need to increase the maximum width of the viewing window. The outer parts of the tree are cut off.
The window is already too small in the eighth generation.
Can you also increase the maximum number of generations? From 15 to 25 or 30 (or even more!!)?
Yes, I know thatâs a lot, but Iâve never had a tree displayed so quickly and would like to test it with 30+ generations.
Iâve never been able to navigate to the older generations so quickly.
I just implemented automatic adjustment of the bounds of the canvas. I also increased the generation limits to 100 (in total 201 generations can be visualized; performance may be suboptimalâŠ).
Please test it and get back to me about any vizalisation issues and performance.
@PLegoux cross-posted to Geneanet : âLook what Santa Claus has put in his sack, a new addon that is semi-graphical for visuals and semi-textual for others:â
GlopGlop ( @grocanar , Ăric) reports (on the Geneanet French language Gramps subforum) that the addon will not display when the project is added to the Addon Manager. GlopGlopâs system is french only.
pour l installarion il faut passer en anglais sinon on ne voit pas le greffon dans la liste des greffons.
Il faut egalement sous Fedora installer les dependances Ă la main quand elle manque mais le message
dâerreur est assez explicite.
Bon câest pas ma came mais je pense que certains dâentre nous le trouveront utile.
Jâai l impression quâil concirrence un peu le cardview non pour la vue graphique.
It works great. 100 Generation are enough.
When setting it to 100 generations, it takes a few minutes for Gramps to finish, but then you can scroll through everything very well
100 generations are enough.
Maybe there is a way you can loosen up the horizontal lines a bit or change the type of connecting lines a bit.
Iâm glad that scrolling etc. works smooth as soon as it is loaded. But itâs unfortunate that it takes multiple minutes to generate the view. Iâll try to optimize that.
I can increase the distance between the lines even more but this will increase the generation distance massively. Iâm not sure if this will help.
You can modify the distance yourself, if you want to play around with it. Modify the numer in the line self.connection_sep = 10 in the file family_tree_view_canvas_manager.py. Most likely, you have to restart Gramps every time after modifying (and saving) the file.
Thank you @ztlxltl, you have brought the user interface into the 21st century.
Running on Mac with no problems.
Hope the âAdd relativeâ has a high priority on your todo list.
@Woody
I dug into the source code of the person edit window and found what I was looking for to display places of events based on the date of the event. I implemented this and pushed it to Github.
@prculleydid a fallback tweak in 2022 to the Plugin Manager Enhanced when Swediish users reported having problems with the Isotammi addon collection. Addon Manager is a later development, uses JSON instead of Text list for the Addons. But is might be a variant of the same problem. Cannot find a MantisBT issue for the GitHub commit. So the fallback issue would be likely to have been overlooked.
Iâm trying to get a few things done first that are relatively easy to implement and have a relatively large benefit for the users (based on feedback). I definitely plan to implement the âAdd relativeâ feature, but Iâm not sure when Iâll do it, as I think it wonât be trivial.
I donât think that this will help. Where did you get the information that an addons.json works as a fallback and that it might help? I cannot find any reference to an addons.json fallback
According to the source code of Gramps, it only looks for files using f"{url}/listings/addons-{lang}.json" (and a 2 character language code).
The link you added by editing your comment seems to point to a paranthesis fix. I looked at the code around the fix and it seems that it also only looks for addon files with a language specification in the file name ("%s/listings/addons-%s.txt"). The current version of the plugin uses Grampsâ own code to retrieve the listing files (see above).
Please bear with me for my reluctance to change something that (now) seems to work for most users. I really donât want to tinker with the working solution unless the change makes sense (to me) and is promising. Sorry (for now) also to @grocanar!