Well, then... quite sad to hear that it's coded differently from the music, but hopefully one day the feature can be added, we can hope <3.
thanks.
ThePaSch wrote: ↑Sat Mar 25, 2023 12:13 amThe main issue with the current implementation of sounds and music is that the trial player currently does not keep track of which sound effects are playing, as sound effects tend to be a "fire-and-forget" thing. They are rarely something you'll want to pause, stop, or otherwise directly control, as most of them tend to be less than a second long. So as of now, once we decide to play a sound effect, we just tell it to play and then promptly forget about it; it'll play itself out, and then that's that.
The same isn't true of music, as it's something you'll very often have playing in the background. We need to be able to stop it, control its volume, and there's only ever going to be one track that's playing at a time, so we do keep track of it - we have to, really. That's why this is easy to do for music, but not quite as simple for sound effects.
A "stop current sound effect" action is additionally sort of problematic since, unlike music, you can play multiple sound effects at the same time, so defining what "current sound effect" means can get a little muddy. The obvious alternative would be a "stop ALL current sound effects" action, but that might, by itself, carry more potential unintended side effects.
All in all, it's certainly not impossible to implement, but also not as trivial as it may seem. Music and sound effects are handled somewhat differently in-code, so a slight refactoring would be in order to accommodate for this. It's certainly not the world, though; the main limiting factor, as with any AAO feature or bugfix, is the availability of any developers who might want to take a stab at it, and the availability of Unas to push the changes to the main site.
