steve wrote:Gale Andrews wrote:It certainly isn't and would mean a lot of code changes for the use case of Audacity not as an audio editor but only as a player application or an application solely for examining the waveform.
Examining waveforms (visually) was one of the original reasons that Dominic created Audacity, so I think there is still some validity in that. Audacity was never intended as an "audio player" and there are much better applications for that purpose.
I'd guess that not warning when there have been no changes at all, would not be too difficult, though it probably would increase the number of support requests: "Audacity is asking me to save my project when I haven't changed anything" when in fact they have changed "something" (such as the zoom level) but they don't realise that that is a "change".
юра00 wrote:The button " Show change history" - I support this idea!
юра00 wrote:So it's not done? And the idea (closing without confirmation) is good.
юра00 wrote:Why is it necessary, if I always choose "No"?
Users browsing this forum: No registered users and 1 guest