On 9/8/09 16:29, Maximilian Albert wrote:
Since my changes already partly achieved this I went ahead and dumped inkscape:output_extension completely from the code base in rev. 22033, where I also committed the other fixes to the behaviour of "Save as ..."/"Save a copy ..." (so that now the various types of save dialogs should remember their file extensions and paths completely independently of each other). It turned out that a good deal of code could be simplified in the process. Although the changes to the code base are not huge, they are non-neglegible, so I'd like everyone to test this thoroughly and report any problems. In particular, please test with all combinations of "Save as ...", "Save as copy ...", "Export bitmap" and various file types, different folders, several documents opened at once, etc. (I did a lot of tests myself but I may have missed some cases). If you are very nitpicky, you can double check that the saved files are actually of the types indicated by their file extensions. Feedback like "works fine for me" is also acknowledged. :-) If people feel uneasy with such a change at this point I'm also fine with holding it off until after 0.47, although I believe it could be a major improvement to this release (and it's been a long-requested fix, too).
On OS X 10.5.8 using Inkscape 046+devel r22058, when opening the 'Save as...' dialog for the first time, it defaults to a path inside the application bundle, which is a big 'no-no' place to ever write files created by the user. A related but different problem is when Inkscape sometimes dumps tmp files or 'inkscape_pasted_image_*.png' inside the bundle and never cleans up (see bug #389262 comment 2).
Moreover, the folder is also stored on a per-save-basis, which might be confusing if you are working with two documents simultaneously each of which you want to successively "save as ..." in different folders (because the dialog always presents you with the folder of the last saved file). Should there be an option somewhere to always choose the current folder and only remember the last used file extension or is this overkill because such a workflow is unlikely?
Once the user saved a file to a certain location, it is used as default when calling 'Save as...' again. Works for me, but for those who adapted their work flow to the old way? Big change. I think adding an option to always default to the current working directory makes sense.
~suv