Make the clipboard persistent

Using the Gramps Clipboard extensively has one drawback. After closing and restarting the app the clipboard is empty again. An option to remember the items would be helpfull.

I second this idea. There are about a half-dozen clipboard items that I
use almost every session. It would be handy to have a way to reload
them in a batch.

The Collections Clipboard add-on gramplet has this ability. Clipboard contents survive a restart of Gramps but not a Tree switch.

1 Like

And all views in both side- and bottom bars can have their own collections clipboards each holding different items.

1 Like

I did not know about this add-on. I gave it a try and it works nicely.
Thanks for the tip!

I see that the contents of the Collections Clipboard are different
depending on which view you are in. For example, the Persons view does
not necessarily have the same contents as the Relationships view. That
might be useful - or not. I need to spend more time getting used to it.

It would be useful if we had get_user_metadata and set_user_metadata methods that could be used by addons like this and the restore hist addon to save and fetch their state in the actual database. Then nothing would be lost when switching trees.

1 Like

Not only for each view. It has a different collection saved for each Gramplet bar: Sidebar or Bottombar. There is no “Category” filtering associated with a view. So they are just different information silos.

This gives the potential for more than 24 collections. So being ‘structured’ in your approach is helpful.

The Dashboard is the only place that allows Multiple copies in the same view with the ability to rename them in the GUI.

That means you can tell the detached/undocked Collections Clipboards apart in the Windows menu. Undocked Collections Clipboard Gramplets from the other views all have identical duplicate listings in the Windows menu.

The Dashboard also remembers which of its Gramplets were undocked and restores them that way … although it doesn’t remember screen positions.

The category view collections clipboards have one reason to be used over the Dashboard. You only have 1 dashboard layout and it is not saveable or reloadable. So if you use different dashboard layouts (like a set of Database Health Gramplets and a different set of Data Entry Monitoring Gramplets) then you have to reconstruct the layout each time you switch workflow modalities.

One trick I use the Collection Clipboards for is for an additional long-term bookmark.

Add the CC to the People sidebar. You can drag-n-drop various people records to the CC. If you right-click on a record on the CC you can make it the active record.

Caution. If you migrate between different database trees, an object in one tree but not in another will disappear from CC’s. if you navigate to that view.

I have been using the Collections Clipboard for a while. Very useful!
Except I think I have found a bug.

If I put more than one citation on the Collections Clipboard, then only
the first one survives a restart of Gramps. All of the place references
come through with no problem. It is only citations that it loses.

So far those are the only two kinds of references I have tried.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.