Win 10 / 11 Pro, Gramps AIO64-5.2.3-r1-aa03f5a
The blurb for the addon ‘Restart where your were last working’ says it causes Gramps to restart on the same view and object where Gramps was previously closed. That’s not how it behaves for me. Regardless of what I’m looking at when I leave Gramps, when I restart it always opens on the dashboard.
Am I missing something?
Did you enable the two “Remember” checkboxes in the General tab of the 5.2 Preferences options?
I think it was because the second tick box wasn’t ticked. Now that’s ticked Gramps is reopening where I left it.
However, those tick boxes, in particular the second one, appear to make the addon redundant because even though I have removed the addon (by deleting the relevant folder from the hidden\AppData.…\plugins folder) Gramps still reopens where I left it.
What exactly is it that the addon is supposed to do?
Support page shows a bit more information:
The ‘Restart where you were last working’ aka RestoreHist (Restore History) addon allows a portion of the Go menu can be made to persist between restarts of Gramps. This addon causes Gramps to restart on the same view and object where Gramps was previously closed.
Usage - Once this addon has been installed it adds no new menus or Gramplet, but allows the last six objects visited to be found via the ‘Go’ menu.
https://gramps-project.org/wiki/index.php/Addon:RestartWhereYouWereLastWorking
[quote=“Gioto, post:4, topic:6444”]
allows the last six objects visited to be found via the ‘Go’ menu.
[/quote] related to the Restore History
@kku , is the Recent Items GENERAL addon related to the Restore History GENERAL addon?
They both cache 6 items of History, one for the Go menu, the other for the Object Selectors.
Do they share cache files? Can they exist independently? Can they be combined into a single addon?
No, the addons are not related. I wasn’t familiar with the Restore History addon.
They do not share cache files. Obviously they can exist independently. In principle they could be combined but I’m not sure if it is a good idea.
Perhaps they could be made to share cache files and eliminate a redundacy?
Your list of ‘recents’ seems to be more consistent and comprehensive. One of the ‘recents’ that the Go menu ignores are: newly created objects… and when users utilize the Edit → Add a ___ , to create a disconnected object, the obvious next step is to attach that object to the tree somehow.
Or, more related to one of your workflows, one of the reasons to save a SuperTool Script to a Note is to edit the script where more rows are visible. But to get to that Note editor, you have to switch to the Notes category (which clears the results in the SuperTool gui) and find the new Note. Then switch back to the original category and re-run the script to reference the results.
Neither ‘recent’ really helps there. Perhaps the context menu in the Clipboard could have a “Clip recent” menu with a submenu of 6 objects?
I often edit or cite something and realize belatedly that there are about to be several more uses of that object. So I should have clipped it.
Anyway, for larger scripts I tend to use the @include feature and store all code in a separate Python file (for example, see the ‘subsets’ script). That file can then be edited with an external editor. All changes take effect immediately. And the external editor can support syntax highlighting which is nice.
It seems to be that the “Restore History” addon does not decide what is stored in the Go menu. It just saves and restores the menu items. The menu is populated elsewhere (in core Gramps code).
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
