Major annoyance (or perhaps my ignorance) with the current version 1.0.2-2 (e86c870879, 2021-01-15) running on a windows 10 pro 64 bit PC. When a new svg file is created and saved, it defaults to the most recent used directory which is perfect.
The problem is that when the export as PNG function is used, the directory defaults to c:\users\myself\bitmap.png - NOT the same directory as I saved the svg file. I do have the preferences - input/output - use current directory for save as checked but that does not seem to apply to the export directory. One has to type out the entire path which is frustrating and inefficient.
Oddly, we also use mac pro and save files in the same location on a network. The export function on the MAC seems to work fine and defaults to the current svg file directory so it is an easy task to co-locate the files. Further if we open a svg file that was generated on the mac on a PC on the same network, when we export an PNG file, the correct directory shows up as default!
Is there a bug in the current PC version? Why does it work if the SVG file was originally generated on the MAC? Could really use some ideas here....
Read as much of that as I can find. Seems like a controversy as to how much of the path is shown in the Export PNG dialogue display. Personally, I don't understand the concerns as every other program I use displays the full path in one form or another so personally I don't mind either way.
My need is for the Export png function to default save the PNG into the same directory where the svg file is located using the same file name as the svg file. The problem is that it saves it to the top level directory and requires that the file name be typed in from scratch. That is the problem on the PC version - works fine on the MAC version. Any way to fix that?
Major annoyance (or perhaps my ignorance) with the current version 1.0.2-2 (e86c870879, 2021-01-15) running on a windows 10 pro 64 bit PC. When a new svg file is created and saved, it defaults to the most recent used directory which is perfect.
The problem is that when the export as PNG function is used, the directory defaults to c:\users\myself\bitmap.png - NOT the same directory as I saved the svg file. I do have the preferences - input/output - use current directory for save as checked but that does not seem to apply to the export directory. One has to type out the entire path which is frustrating and inefficient.
Oddly, we also use mac pro and save files in the same location on a network. The export function on the MAC seems to work fine and defaults to the current svg file directory so it is an easy task to co-locate the files. Further if we open a svg file that was generated on the mac on a PC on the same network, when we export an PNG file, the correct directory shows up as default!
Is there a bug in the current PC version? Why does it work if the SVG file was originally generated on the MAC? Could really use some ideas here....
Exported file name should be saved in svg as relative path; current behavior may leak private system information (#804) · Issues · Inkscape / inkscape · GitLab
Aero,
Read as much of that as I can find. Seems like a controversy as to how much of the path is shown in the Export PNG dialogue display. Personally, I don't understand the concerns as every other program I use displays the full path in one form or another so personally I don't mind either way.
My need is for the Export png function to default save the PNG into the same directory where the svg file is located using the same file name as the svg file. The problem is that it saves it to the top level directory and requires that the file name be typed in from scratch. That is the problem on the PC version - works fine on the MAC version. Any way to fix that?
Todd
Seems you will be one step closer to what you want in 1.1 beta, but you may have to reopen the export panel every time to make that happen.