New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
when built-in SVGs are added to a composer layout paths should be relative to the install directory #14042
Comments
Author Name: Paolo Cavallini (@pcav)
|
Author Name: Tim Sutton (Tim Sutton)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Paolo Cavallini (@pcav)
|
Author Name: Paolo Cavallini (@pcav)
|
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Alister Hood (@AlisterH)
Now it is always stored as an absolute path. |
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman) End of life notice: QGIS 2.18 LTR
|
Author Name: Alister Hood (@AlisterH)
Original Redmine Issue: 4056
Affected QGIS version: master
Redmine category:map_composer/printing
When a built in SVG is used as a layer symbol, the path is stored in the .qgs file as a path relative to the QGIS install directory, regardless of whether the project is configured to use absolute paths or relative paths. This is good, as it means the project file is portable between instances of QGIS installed on different platforms or in different directories.
When a built in SVG is added to a composer layout using the "add image" button, the path to the SVG is currently stored in the .qgs file as an absolute path or as a path relative to the .qgs file, depending on the project configuration. This is bad - if you open the composer layout on a system where QGIS is installed to a different location then the SVG is missing. If the SVG is built in, the path should be stored relative to the QGIS install directory. If the SVG is in one of the user-defined paths then it should be stored relative to that location.
The code changes for #13214 might be a helpful reference
The text was updated successfully, but these errors were encountered: