when I put a link to a local file into my text in the Scrivener editor, I observe a phenomenon that bothers me.
Dragging a file from the main Finder window into the editor produces a link in the Scrivener editor that looks like this:
is fine as long as I use Scrivener on this one computer. However, working with Dropbox I use my projects on several computers, having the files and folders synched and mirrored on them so the file structure is the same on all machines.
Opening the project on one of the computers and clicking the link will fail, as it cannot find this file id.
I have found a few workarounds, though.
In oder to get a link such as “/Users/myself/whatever folder/this file” (which would be portable) I can select the link produced, right click, edit link. In the window appearing, the actual path is shown, so I can see it is actually stored somewhere but not active when clicking the link. Now, not changing anything, but just hitting “Return” in that edit-link-window will cause the actual link to convert to the desired format!
Another possibility is not to drag the file from the main Finder window, but from the status bar below at the bottom of the Finder window. There, you can show the path of a file, and dragging the file icon from there into the Scrivener editor will produce a link that is “correct” right away, i.e. it shows the path and not a file id.
A third possibility is to drag the file icon from an open document using the icon in the title bar of that window.
Now, why is the most obvious method of dragging a file into Scrivener, in oder to produce a link, failing in this way? Is this a desired behaviour or part of the consequences of using Apple’s native editor capabilities in Scrivener? Or can this be healed in Scrivener itself, which would be marvellous … since despite knowing the limitation I tend to forget about it and link files again and again, just to see the link fail next time I use it.
By the way: The bookmark tool in Scrivener’s Inspector does it right. Regardless from where I drag the file, it ends up as a nice file path and can be used from everywhere.