From: david <gn...@ha...> - 2010-07-09 19:49:58
|
Chris Cannam wrote: > On Fri, Jul 9, 2010 at 7:45 PM, Abrolag <ab...@us...> wrote: >> It was with some surprise (and annoyance) I found that RG had created a >> 'rosegarden' directory there and stuffed it full of audio without even >> so much as an 'ahem'. This is why the archive I sent to doesn't contain >> those files. I was not expecting anything to be there. > > I believe the difference is that former versions would refuse to do > anything audio-related until you had set an audio file path (which is > done through the document properties), whereas the newer versions will > default to ~/rosegarden if no audio file path has been set (but you > can still set one if you like). > > One problem with this of course is that now there's no indication that > you ever need to set the audio file path, and no way to discover that > the option is available, and so it's more likely to remain unset. > > This whole subject has long been a thorny one. What's the best solution? Not that I've used RG's audio features yet, I think I'd go back to the old way, with maybe one variation. If audio file path isn't set when user first tries to use audio, RG asks them to set the audio file path. Give user a nice little file system navigation button to do it with that defaults to a rosegarden folder user's home directory. After it's set, go on and do whatever audio thing the user is trying to do. -- David gn...@ha... authenticity, honesty, community |