Yes, the problem is that the user is unaware that those audio files have been lost—they only know that they cannot proceed, but they don’t know why.
Suddenly, and for reasons unknown to them, the user finds themselves unable to perform an action—such as changing a template—even though that action has absolutely nothing to do with the missing files.
The user cannot resolve the issue because they are not even aware that something is wrong. This should never prevent the "Accept" action from being taken; just as, for instance, the loss of a color scheme or a QSS file does not currently disable the "Accept" button.
If the files cannot be found, the system simply shouldn't load anything, leaving the "Accept" option fully functional.
And if, for example, the user were to stop hearing the metronome, they would likely check the settings—at which point they might realize that the WAV files had been moved by mistake.
Yes, the problem is that the user is unaware that those audio files have been lost—they only know that they cannot proceed, but they don’t know why.
Suddenly, and for reasons unknown to them, the user finds themselves unable to perform an action—such as changing a template—even though that action has absolutely nothing to do with the missing files.
The user cannot resolve the issue because they are not even aware that something is wrong. This should never prevent the "Accept" action from being taken; just as, for instance, the loss of a color scheme or a QSS file does not currently disable the "Accept" button.
If the files cannot be found, the system simply shouldn't load anything, leaving the "Accept" option fully functional.
And if, for example, the user were to stop hearing the metronome, they would likely check the settings—at which point they might realize that the WAV files had been moved by mistake.