Ed, I don't think any changes to mod-script-pipe have stopped the modules directory being used as the working directory. On XP using SVN and an initialised .cfg, the file open/save dialogues open into the Modules directory. If I delete the Modules directory, the dialogues open into the directory of my file manager program.Edgar wrote:Gale, Audacity's behavior is different today because (since the recent check-in of all the changes to mode-script-pipe) the "modules" folder is not hijacking the current working directory anymore.Gale Andrews wrote:As far as I understand it, (this is how it works on XP), the Save Project window always opens at the directory from which an .aup project file or audio file loaded was loaded. Otherwise, it will fall back to the working directory the first time Save is used, or after first use, to the last used directory. [...]
From occasional use of Windows 7, I don't get the impression that the Export/Save/Open directories behave differently - would someone like to test that?
With the new Windows 7 virtual filesystem's Save dialog being used for Save Project As, here's what happens:
* If you start Audacity (by double-clicking on its icon or from the CLI) for the very first time ever and immediately "Save Project As" the Save dialog will open defaulting thing to the Desktop (or possibly the user's Documents folder, it is very difficult to be absolutely certain I am testing a "very first time ever" Audacity).
* If you save an Audacity project in a folder, exit audacity and delete that folder, start Audacity and "Save Project As" the Save dialog will open in the user's Documents folder.
* If you start Audacity by double-clicking on a project icon then choose "Save Project As" the Save dialog will open in the folder of that project (even if you have saved a Audacity project somewhere else in the meantime).
So apart from the fact that Windows 7 (and Vista?) will open into the user's Documents directory, the other behaviour you listed seems the same as on XP.
Gale