That's comforting! BTW that version has an undocumented feature (or bug): new project window cascading/marching has been turned off – all new project windows open at the same size and location as the active project window. I have a new build which has not yet been delivered to the client which turns this feature back on and back ports a small handful of 2.0.6 bug fixes. I am thinking about making this a preference.
Gale Andrews wrote:
I didn't realise the switching of the export folder to that last imported/opened from was in that version, so I tried it.
A very desirable feature I think, especially when dragging in also switches the folder. I can already think of an enhancement option for it - don't make it per project, so that if importing from folder A into Project A then from folder B into Project B, exporting from Project A opens the export dialogue at folder B.
This would require some thought; what happens if you Import from folder A into Project A then import from folder B into Project B and then import from folder C into Project C – and you want the dialog to open in folder B? This is almost
* the exact dilemma the client brought me; initially I had it working the way I liked it, the client had me change it after internal beta testing then, after release, got enough feedback from users to have me change it back the way I originally had it. I set up the code so that a preference switch would be trivial but the client chose not to use a preference switch.
*This was actually in regard to multiple imports into a single Project but the dilemma remains the same.
Gale Andrews wrote:
Remind me - what else than the need for code refactoring stands in the way of this folder-switching? Is it dependent on the Windows 7 Open/Save dialogue?
The folder-switching code (the client calls this "Smart Folders"), excluding some similar code I have added to Export Multiple, is fairly simple as it exists now; each project has its own new variable which stores the Import folder's complete path (deriving this path can get tricky on Windows), each of the three places where the code Imports needs to have a few identical lines to derive and store this path information. At some point the Developers plan on re-factoring the Import code so that instead of three almost identical sections of Import code there is only one.
Gale Andrews wrote:
Do you know why we don't we use that newer dialogue now for the relevant WinNT versions? It doesn't seem to have any bugs when you navigate to another folder.
That newer dialog only exists on Vista service pack 2 and newer Windows; It is easy to determine if we are on Vista or Windows 7 but it is very difficult to programmatically determine the difference between Vista service pack 1 and Vista service pack 2. There is a huge amount of new code added to the current Audacity code base in order to implement the newer dialog
Gale Andrews wrote:
I changed the "Unselected Peak" background colour but this made the Selection Toolbar TimeText controls just a small "bump" where the controls should have been.
I have fixed this. Vaguely, what is happening is that the default Selection Toolbar TimeText controls end up storing a system default font size which is very tiny and makes the controls very small. The fix was to force the TimeText to have a reasonable default font size.
