> Oops, sorry.  I'd noticed it when I was fiddling with the crash on close
> problem and I just thought it was old.  Would you like me to put it back?

No, it might as well stay just the way you changed it to and so not 
confuse other people with functions that aren't available....  Like I 
said, it's no problem.  Experimental.h is for our own local variations. 
  You can be sure I keep a copy that's even more different to CVS for 
tinkering.

What *would* be a problem would be if the
#include "Experimental.h" were to be removed from certain .cpp files. 
Sure, they're not used in the normal builds, but they darned well are 
used in experimental builds.

--James.

Leland wrote:
> On 9/17/06 11:58 AM, "James Crook" <[EMAIL PROTECTED]> wrote:

>> There's no problem at all with removing the VOCAL_STUDIO experimental
>> bits, but they're not so much obsolete as not-yet-ready.

>> The idea of experimental.h is that in our own local copies of Audacity
>> we can enable additional features which are not suitable for main CVS.
>>    The vocal studio has a vowel quadrilateral display - but it is not
>> hooked-up to anything and I've not looked at it for over a year.

> Oops, sorry.  I'd noticed it when I was fiddling with the crash on close
> problem and I just thought it was old.  Would you like me to put it back?

> Leland


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Audacity-cvs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/audacity-cvs

Reply via email to