This read-only archive contains discussions from the Adding Feature forum.
New feature request may be posted to the
Adding Feature forum.
Technical support is available via the
Help forum.
-
Gale Andrews
- Quality Assurance
- Posts: 41761
- Joined: Fri Jul 27, 2007 12:02 am
- Operating System: Windows 10
Post
by Gale Andrews » Wed Nov 26, 2014 11:32 am
steve wrote:FWIW I slightly favour:
Code: Select all
<wavetrack name="Audio Track" WaveTrackDisplay="Spectrum" channel="2" linked="0" mute="0" solo="0" height="150" minimized="0" isSelected="1" rate="44100" gain="1.0" pan="0.0">
over
Code: Select all
<wavetrack name="Audio Track" WaveTrackDisplay="0" " channel="2" linked="0" mute="0" solo="0" height="150" minimized="0" isSelected="1" rate="44100" gain="1.0" pan="0.0">
given that it is more readable
To be completely unconfusing, the friendly name used should be the same as in Tracks Preferences.
steve wrote:as far as I'm aware, not documented in the manual.
You mean the AUP file syntax is not documented? No it isn't - and if it was, I'd expect us to write "RMS" in the AUP not rms.
Gale
-
Edgar
- Forum Crew
- Posts: 2043
- Joined: Thu Sep 03, 2009 9:13 pm
- Operating System: Windows 10
Post
by Edgar » Wed Nov 26, 2014 5:32 pm
Steve, you now have commit rights; are you willing to commit either the man or machine solutions?
Leland on -devel wrote:
steve on -devel wrote:My question is, man or machine? Do we want the simpler code, or a more complex but human friendly version?
Man. Sometimes enums get rearranged.
Rearranging enums destroys any chance of backwards compatibility and should
never be done. The whole point of enumerations is that you can add new ones without breaking backward compatibility.
-Edgar
running Audacity personally customized 2.0.6 daily in a professional audio studio
occasionally using current Audacity alpha for testing and support situations
64-bit Windows Pro 10