On Fri, Aug 7, 2009 at 7:50 PM, Maximilian Albert < maximilian.albert@...1439...> wrote: I'll test it now. Results should be forthcoming in under an hour. P.S.: I believe the export dialog doesn't remember its own path yet The export dialogue does it differently; if exporting the whole drawing or an object, that object saves its own path, which can be a bit of a nuisance cross-platform - e.g. one of the inkscape website designs I was looking at was then automatically setting it to /home/..., but generally that's very useful. So to answer your question, yes it is desired to store the path, but I think it already does for Page and it does for Drawing, inside the inkscape namespace in the SVG. I'm happy with how it does it (or did before you committed anyhow in case you changed it.) You probably knew that anyway :P -- Chris Morgan <chris.morganiser@...400...> I don't need a quote in my signature. It's hard enough surviving as it is without having to find a meaningful quote. Will you forgive me? Or don't you read this bit?

2009/8/7 Chris Morgan <chris.morganiser@...400...>: Oops, sorry. I accidentally added a parameter to the wrong method in the .h file but didn't notice since compiling on Linux disregarded the relevant sections of the file. It should be fixed now. Could you try again? Thanks for your help! Max

2009/8/8 Maximilian Albert <maximilian.albert@...1439...>: I haven't heard back from anyone but I've discovered the discusion of the following bug report which says that inkscape:output_extension should be eliminated: https://bugs.launchpad.net/inkscape/+bug/170966 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). One remark concerning the elimination of inkscape:output_extension: We now don't store the file extension on a per-document basis any more but rather on a per-save-action basis. That is, if you have two documents open at the same time and save one of them using "Save as ..." with a certain file type, switch to the other document and invoke "Save as ...", it remembers the just used file type. I hope this is desired, since it's also requested in LP #171932, but I thought I'd mention it. 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? And another thing: When saving a newly created file for the first time, I made the dialog propose "Inkscape SVG" as the file format, regardles of what previous files were saved as. I think this reasonable, but do others agree? Thanks for any feedback! Max

On Wed, Aug 12, 2009 at 7:26 AM, ~suv<suv-sf@...58...> wrote: It should warn you in batch export if the target path does not exist. But otherwise this is the expected behavior. I want to be able to mass-export from one master SVG to many PNGs in different dirs, and I want it to remember those dirs per object. I propose to rename this to "Batch export should be more explicit about where it exports stuff". The point of export hints is that they are stored per-object. Storing the IDs and export data for all exported objects in all documents in prefs does not sound too elegant and will be hard to keep up to date - any deletion of an object and any ID change will have to go to prefs and update that data so it stays in sync. I don't know if it makes sense to implement all this. Once again: I agree to add a preference option to save export hints (on by default), and/or a command to remove all hints if you want to share your file. But otherwise, the current system is simple, straightforward, and saves a lot of time in real work. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

On 12/8/09 14:01, ~suv wrote: Fix in SVN revision 22060 confirmed - on OS X Inkscape 22062 now opens the 'Save as...' dialog at first run in $HOME, like in previous versions (tested: r21924, r22028). thanks, ~suv

On 17/9/09 17:09, Maximilian Albert wrote: I'm testing your patch now (with r22271). Question (just to be sure I fully understand the patch): 'Save as...' and 'Save as Copy...' use independent settings i.e. 'Open...' and 'Save a Copy...' always default to its 'Last used' folder, whereas 'Save as...' can be toggled between 'Current' and 'Last used'? BTW - I get this warning when compiling (in my build logs since 22058, not present in 22028): It causes no error and compiles fine. Seems related to your latest commits in rev. 22033? ~suv

On 1/10/09 09:10, Maximilian Albert wrote: Patch tested and confirmed with Inkscape 0.46+devel r22293 to r22349 on OS X 10.5.8 The patch works fine and improves file handling in Inkscape IMHO. My use of the new option: once set to "use current directory for 'Save as…'" I never felt the need to go back and use 'most recent'. It takes time though to remember the different ways the file dialogs now behave: open: most recent - good save as: current - good save a copy: most recent - good for repeated exporting to fixed folders, - less for backups/variants in current or below import: most recent - ok I would certainly vote to include this patch for 0.47 as an important option though I still like the idea to have 'current' listed under Places in the gtk-filechooser dialog - i.e. a shortcut for the current folder available for every file command (open/save/copy/import). ~suv

On Fri, 2009-10-02 at 18:58 +0200, ~suv wrote: Reviewed, tested, and committed (as the behavior is much better imho). I did slightly modify the tooltip per Max's comment too. Cheers, Josh

On Fri, Oct 2, 2009 at 6:20 PM, Joshua A. Andler <scislac@...400...> wrote: Can you or anyone please fill a Release Notes entry for this? Thanks! -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

On 9/8/09 16:29, Maximilian Albert wrote: Any news on this? My issue with the new way the folder is stored on a per-save-basis: I no longer have a way to quickly figure out where the current document is located on disk without saving it (i.e. change, save, undo) in order to see the full path name in the window title bar. Before I could open the "Save as..." dialog to immediately see the current working directory, now I have to switch to 'Recently Used' in the file chooser dialog and hover over the files to read the info in the tool tip. This is annoying if you open a drawing from the 'Open Recent' list and e.g. want to save a snapshot/backup/variant of the document in the same folder as (or relative to the folder of) the original. And I have 'lost' several files this way because they weren't saved in $CWD where I expected them to be: if in a rush I tend to forget to check the location (or compare it to $CWD) in the 'Save as...' or 'Save a copy...' dialogs and have to resort to the file manager to locate the misplaced copies ;-) Some ideas: - add an entry for the 'current working directory' in the file chooser dialog (like 'home', 'system' or 'templates' under 'Places') - always display the full name (path+filename) in the window title bar - add a shortcut to display file info (full path + file name, maybe size or last Mod date) in the status line - add tool tips to the files in the 'Open Recent' list as in the file chooser dialog, displaying full path + file name To choose in the preferences between 'always use current folder' or 'always use last used folder' doesn't help as IMHO it often fits the work-flow to use the recent folder. ~suv

Hi Max, On 17/9/09 17:22, Maximilian Albert wrote: No, it's my fault - my two earlier messages are contradictory (in hindsight) - consider the 3 weeks in-between as learning curve... On 12/8/09 14:01, ~suv wrote: On 3/9/09 19:01, ~suv wrote: Basically I learned to appreciate the 'last used folder' default (after getting used to it). To have the choice 'last used folder' and 'always current working directory' is be a viable option but would force me to choose when I only miss a minor additional feature for the 'last used folder' default: How do you figure out in an easy way what the current working directory (path to the currently open document) is - without unnecessarily modifying it to be able to save it? There may be several reasons why you want to know this - mine mostly was to avoid additional later reorganization of the files in the file manager because a save/export operation (e.g. in a second document window) placed the files in the wrong folder. Scenario: open a document from the 'Open recent...' list 1) you want to export it (save a copy) to different formats in a folder relative to its location 2) you want to extract embedded images into the same folder (no file browser available - you need to know the path) 3) you want to open a related second drawing stored in a (sub-)folder of the currently open drawing (but the file browser dialog opens in the location of a project you worked on yesterday) 4) ... My preferred solutions would be a) always display the full path in the window title b) add a 'Current' location to the places in the gtk file chooser (like home, system and templates) Maybe you have a better idea or can show me existing alternatives? Or convince me that no one else ever needs to know the $CWD ;-) ? Thank you for considering my thoughts on this, ~suv

2009/8/9 bulia byak <buliabyak@...400...>: Yes, right. I got a bit confused from reading the code. :-) I didn't know that there are two types of export dialogs, one of which mimicks the regular Save dialog and is deactivated by default. I have never tried it anyway. Does it work and does anyone use it? Max

2009/8/9 bulia byak <buliabyak@...400...>: I'm not sure if I understand which dialog you're referring to because it sounds like the one you're describing is in regular use. I'm talking about the one which is defined in ui/dialog/filedialog.cpp starting from line #240 (as of rev. 22036) and which has #ifdefs around it. Anyway, I just tried it and it's apparently not currently used since Inkscape didn't even compile when I uncommented #define NEW_EXPORT_DIALOG. :-P Now I put the whole code which refers to this dialog between #ifdef's and fixed the build when NEW_EXPORT_DIALOG is defined. However, the dialog crashes when trying to export any file. I'm wondering if it can be scrapped completely since it's apparently not in use and doesn't seem to have been touched since revision 12671. Any opinions? Max

2009/8/10 Yann Papouin <yann.papouin@...400...>: Damn yes, I missed those. Thanks for the patch, it's fixed in SVN! Max

On Sun, Aug 9, 2009 at 1:56 PM, Maximilian Albert<maximilian.albert@...1439...> wrote: I remember there was some activity a couple years ago for a new export dialog - I remember seeing mockups, at least. I'm not sure what to do with the disfunctional code - of course the first instinct is to delete it, but I think we should first contact those who added it, in case they or anyone else might be interested in resuming the work. Of course the new export dialog must, at least, provide all the functionality of the current Ctrl+Shift+E. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org