The advantage of Relative Path is that it doesn't matter what folder Able Project and Baker Project are in that information is not saved and Revu has no knowledge of it. Since Able Project and Baker Project are in the same folder ( Projects), the relative path from Able file.pdf to Baker file.pdf is simply go up to their common folder ( Projects) and from there, go into the Baker Project folder to find Baker file.pdf. In the Relative Path example above, the folder structure looks like this: In this case, Revu does not know what drive Baker file.pdf resides on what it does know is that, starting from the current location of Able file.pdf, it needs to go up one folder and find a folder called Baker Project. On the other hand, the location of Baker file.pdf can be saved according to its position relative to Able file.pdf by turning Use Relative Paths on, as shown below.
It doesn't matter where Able file.pdf is when the full path is saved so long as it's anywhere on the same computer, it will be able to find Baker file.pdf (it still needs to be on the same computer in this example, however, so that it is looking in the correct C:\ drive). The full folder path is saved (C:\Projects\Baker Project\Baker file.pdf). For example, in the hyperlink configuration shown below, Use Relative Paths is turned off, so the full path to the linked file ( Baker file.pdf) is used. Most people are already used to Full Paths: this saves the full folder path to the file. The first thing to understand about Relative Path vs Full Path is that they are just different ways for Revu to save the location of a file.
The distinction becomes important when either or both files are moved.įor the purposes of this discussion, we'll consider the case of a PDF ( Able file.pdf) with a hyperlink on it that is configured to open a second PDF ( Baker file.pdf), but the principles apply to Profile dependencies the same just substitute Able file.pdf for the Profile and Baker file.pdf for the dependency. For most users, either choice will work fine in most situations. To this end, Revu has two ways of storing the locations of files: by the full path to its folder (Full Path), or relative to the location of whatever is accessing it (Relative Path). Similarly, there are aspects of Revu's Profiles called "dependencies" ( tool sets, hatch patterns, line style sets, and bookmarks Structures™) that exist as separate files (so they can be shared) in order to access them when in a given Profile, Revu needs to know where these dependency files are. For example, when a hyperlink is configured to open another PDF, Revu needs to know where that PDF resides. Sometimes Revu needs to store information regarding the link between two files. Understanding Relative vs Full Paths Understanding Relative vs Full Paths