Закрытие программы без подтверждения

Как сделать, чтобы после закрытия, то есть нажатия на белый крестик в красном квадрате в правом верхнем углу, происходил бы сразу выход (без сохранения), а не появлялось бы окно: “Сохранить изменения перед закрытием, да - нет”. You can answer in English, I’ll translate.

I do not speak Russian. And no, you can’t disable that warning. It’s a feature request (which we won’t agree to except perhaps in some specific circumstances). There are too many users who delete files after importing them.

But Audacity is open source so you can change it how you like if you learn C++ and recompile it. Or you can pay a commercial price to have a developer make the change for you.


Thank you!

Thanks for an answer, but why not just add one more checkbox in Confirmations dialog
meaning “Closing a program without asking”?

It’s so annoying, I have to open and close Audacity ten times a day,
and it got me to confirm closing every time.

Any decent program should have such choice in my humble opinion.

When users delete their files after importing them, after having enabled your new option by mistake, they won’t be calling Audacity a “decent” application.


OK ,but this does not make a point.
If user enable this option by mistake they should not blame this program.

If we go farther such way: the user could have answered ‘No’ “by mistake”
when asking saving their project and blame Audacity for this.

Of course, that happens too. There are a number of long Forum topics about exactly that.

Your vote will be counted. But I don’t think we will ever change to “trust the user”. We might do something like give an option to disable the warning if the complete project has been exported with no further changes.


I agree, but unfortunately that is not the case. Users frequently make mistakes and blame Audacity for their mistake :frowning:

When Audacity can detect that the user may have made a mistake, and, if it is a mistake, that mistake will cause the permanent loss of their work, then I think it is a reasonable compromise for Audacity to warn the user of the possible mistake. That is the case when closing an unsaved project.

I do think that it should be possible to close the project without the warning if the project has not been changed. However, that is not as simple as it might sound. Audacity records such things as the “zoom level” and the “selection” as “changes” (which are written to the AUP file). If a user has only changed the selection, the user would probably not consider that to be “changing the project”, but for Audacity the project has changed. Audacity would need to be able to identify if any “functional” changes had been made to the project. For example, changing an “envelope” will change what the project sounds like, so that is a “functional” change and that should prompt the warning, whereas “changing the time format” has no lasting effect on the project, so that should not prompt the warning. Audacity does not distinguish between changes that permanently alter the project and other changes, so that is a lot of additional code that would need to be written.

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.

A mode where Audacity launches with whatever saved project or unsaved content it had open last time is I think one possibility. It “solves” more than the use case of Audacity as a player application and is probably less coding work. It would need a lot of thought though.


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”. We could possibly work around that if the prompt included a button for “Show change history”, which would allow the user to decide if they want to save the changes or not. I think that is not a bad idea as we would like to be able to save the “History” log anyway.

The button " Show change history" - I support this idea!

The zoom level is not on the Undo stack, so not in the History window. In fact people complain when they open a project, change the zoom level or cursor position, then that change cannot be saved in the project unless they make some edit that triggers undo.

Changing the track gain is an action that may look like “nothing” but triggers Undo.

What you are suggesting is extremely dangerous giving the known propensity of users to delete files after importing them. If they have exported the project contents without further (audio) changes, yes we might then let them quit without saving.


OK noted thanks.


So it’s not done? And the idea (closing without confirmation) is good.

It is hardly a priority when only two people want a button in Save Changes to show history.

But you can always send us a Git Pull Request when you have coded it for us.


I have in mind to close immediately without message:

Why is it necessary, if I always choose “No”?

Already answered in the previous part of this topic.


Well, if you can’t close the program without confirmation, can you at least make for “Save project” the default “No” instead of “Yes” (so you can press Enter)?

Gale will not be replying as he passed away last year.