Need help doing a cross-OS (Linux & Mac) verification

I can do Windows testing but need help from a couple users to look at a feature in Linux and macOS

There are GTK options to use file location box instead of breadcrumbs in the File Manager dialogs.

Some time ago, the wiki added a line listing in the Handy Shortcuts section of the keybindings page for toggling between the breadcrumbs and filepaths textbox.
The macOS had to be corrected to ⌘ Cmd+L.
But I’m not sure the Linux Ctrl+L keybinding was confirmed.

The toggle seems to be implemented but the feature doesn’t work as one might expect.

When I toggle from breadcrumbs in a Windows OS file manager dialog, the text box is populated with the fully qualified filepath for the current folder. But in Gramps for Windows, the text box is blank. That seems wrong. (Sometimes the OS version demanded some weird additional steps when trying to populate with a fully qualified path but starting from a File Selector for relative paths. In Gramps, the add Media objects would be a relative path variation leveraging the Preferences’ Media base path.)

I’m not sure how much the technique Paul describes for using Environment Variables applies to just the CLI (or Preferences form fields) versus file location textbox in the Gramps dialogs.

Same here under Linux (Debian 10) in Gramps 5.1.2.

1 Like

I have MacOS 10.14.6. It’s Ctrl+L, not Cmd+L, that causes the breadcrumbs to change to a locator box in the dialog to add a media object. But it’s not a toggle; to get back to the breadcrumbs, I have to press Esc.

1 Like

Also, the text box is not populated, but I can tell it’s pointing to the current folder because when I start to type a file name, it gives a list of files starting with whatever I type.

1 Like

Have been doing some more digging into the GTK file selector dialog. There is a Bookmarking feature for adding buttons to the dialog. However,the file is not where expected or named as predicted. I was expecting a bookmark file in with the rest of the Gramps customizations. It wasn’t there.

But some forums say that there would be a file named gtk-bookmarks.py at the top of the User folder. Instead, I found a text file (with no extension) with the following file on my Windows box:

C:\Users\<username>\AppData\Local\gtk-3.0\bookmarks

The bookmarks file has one line per button. Again, in Windows, the path for a button looks like:
file:///C:/Users/<username>/folder/subfolder ButtonName

Gramps currently lacks an option to name the Button at the time of creation. It leaves that parameter off and the GUI just repeats the subdirectory name. But, you can Rename the button (or edit the configuration file directly) if you want specific aliases on the buttons.

The obvious candidates are the Examples folder included with each installation and a couple paths from from the Preferences:

  • Family Tree: Backup path:
  • General: Base path for relative media paths:
  • Example file subfolder: C:\Program Files\GrampsAIO64-5.1.3\share\doc\gramps\example

My bookmarks file has the following lines:
file:///C:/Users/DistrictSupport/Desktop/Archives/GrampsBackup2020 Backups
file:///C:/Users/DistrictSupport/GrampsMedia Media
file:///C:/Program%20Files/GrampsAIO64-5.1.3/share/doc/gramps/example Examples

Another possible bookmark might be the examples folder on the GitHub archive:

https://github.com/gramps-project/gramps/tree/maintenance/gramps51/example/

About that : what about proposing to load the test tree during gramps install ?

Best regards.

The test tree example.gramps has to be imported into a Tree. It does not exist as a database as part of the install. And the Import menu command does not exist until a Tree is created.

So right now, that wouldn’t be possible.

I just filed a Feature Request to make Import more accessible for 1st time users. It seems logical to me that Import menu should be there from the start. And if you try to import before creating a Tree, Gramps should just create a Tree – auto-named to indicate the data was imported.

2 Likes

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