Is your Place Tree sometimes slow?

[GeorgeWilmes]

@emyoulation

Actually, those are People rather than Places

In that case, I think those warnings are coming when the tree view of the People category is being populated. The text of that warning is in treebasemodel.py, with the comment:

    """
    How to handle adding a node a second time
    Default: if group nodes can have handles, it is allowed to add it
        again, and this time setting the handle
    Otherwise, a node should never be added twice!
    """

[emyoulation]

Yes, that’s the first time I’ve seen that “twice adding a node” error. I think that it scrolled anything related to the Places off the CLI terminal window & overflowed the buffer. (Although I don’t recall THAT ever happening before either.)

I had just been HOPING that the terminal would have something useful.

Since no one has mentioned a log file I could access, I guess I’ll cycle Gramps and start working again.

[emyoulation]

Workaround: hack the Place Selector so that it doesn’t use the Place Tree Model

@DaveSch

edit the file (version 5.1.5)

gramps\gui\selectors\selectplace.py

change line 36

from ..views.treemodels.placemodel import PlaceTreeModel

to

from ..views.treemodels.placemodel import PlaceListModel

---

change line 62

return PlaceTreeModel

to

return PlaceListModel

Since using a PlaceListModel instead of the PlaceTreeModel is a workaround, my Place hierarchy has something wrong or the model’s code has a problem.