On 17/9/09 17:09, Maximilian Albert wrote:
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.
I agree. Attached is a patch which adds an option to the Preferences to choose between both kinds of behaviour. I renamed the "Autosave" page to "Save" and added the option there because it seemed most logical; please let me know if you disagree. I'm not sure if this patch is acceptable during freeze since in some sense it adds a feature, but I'd regard it more as a bug fix so I'm sending it anyway and leave it to the release wardens to decide. BTW, feel free to change the wording in the tooltip because I have the feeling that it doesn't sound as smooth as it could (that's the disadvantage of not being a native speaker).
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):
extension/system.cpp:558: warning: enumeration value ‘FILE_SAVE_METHOD_EXPORT’ not handled in switch
It causes no error and compiles fine. Seems related to your latest commits in rev. 22033?
~suv