inconvenient default path for extension 'Extract Image…'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Fix Released
|
Low
|
jazzynico |
Bug Description
Inkscape 0.47+devel r9287 on OS X 10.5.8
The default path+filename of the extension 'Extract Images…' is given as 'none' in the corresponding inx file. Unchanged, this results in extracting the image into the shared extensions directory (which - as of recent revisions - is the working directory of the spawned python process). The default filename extension (*.png) is not added (contrary to the explanation in the dialog).
This extension should either default to $HOME or 'Extract Image…' should be moved from the extension system to a native Inkscape command so that the images can be saved in the same location as the SVG document they have been embedded in. AFAIU it is not possible for script extensions to obtain the actual full path of the current SVG file opened in Inkscape - extensions only see a copy of the file in $TMP.
The extension 'Export Layer Slices…' (see bug #169985 “Slicing pluging (for web and whatnot)”) defaults to $HOME (or '~') for the export path - maybe the extension 'Extract Imges…' could be changed similarly (i.e. if the filename is relative, make it relative to $HOME and not to the working directory of the python process) - until extracting images is handled by Inkscape internally?
Related branches
summary: |
- inconvenient default path for extension 'Extract Images…' + inconvenient default path for extension 'Extract Image…' |
Changed in inkscape: | |
status: | Fix Committed → Fix Released |
Confirmed on Windows XP, Inkscape bzr rev. 9315.
The filename extension is correctly set on Windows, but the image is extracted in the share\extension folder.