It's that I don't want to change this behavior twice, basically. It's a disruptive enough behavior change that I'd rather not change it now and then turn around in a little while and change it again. Not related to what the *correct* behavior is, but rather that there's a certain behavior people currently expect (which is also the way it's been behaving for more than a decade) and I don't want to suddenly change it in a minor update and then change it again when we revisit the problem more deliberately.
What you're describing as far as "what you hear is what you get" only works if you're doing tone practice as a listening test, which is not how everybody uses that feature. For someone who's reading tones on the screen and learning them, they're going to want the tones they saw on the screen to be marked as correct, not the tones they hear. We could of course simply accept both answers, but then people might be annoyed that an answer that didn't match what they heard was nevertheless marked correct because it matched the way the card was written.
So I totally agree that it would be better if it marked you correct on a listening test based on what you heard, but it's not a change we're likely to make in a minor bug-fix update, because it probably requires a new setting and a bunch of other changes and I'd rather not do it haphazardly now + then revisit it again later.
What you're describing as far as "what you hear is what you get" only works if you're doing tone practice as a listening test, which is not how everybody uses that feature. For someone who's reading tones on the screen and learning them, they're going to want the tones they saw on the screen to be marked as correct, not the tones they hear. We could of course simply accept both answers, but then people might be annoyed that an answer that didn't match what they heard was nevertheless marked correct because it matched the way the card was written.
So I totally agree that it would be better if it marked you correct on a listening test based on what you heard, but it's not a change we're likely to make in a minor bug-fix update, because it probably requires a new setting and a bunch of other changes and I'd rather not do it haphazardly now + then revisit it again later.