I fully agree with the fact that a setting should be used only for one purpose and sharing is not a good idea.
Nevertheless I have couple of remarks:
That’s clearly THE reason not to share the same setting for various behaviors. Although for me the double click on the stop button to stop immediately makes the trick. I doubt the single tap will happen anytime soon as the current behavior is the result of a lot of discussions.
But if we split the two settings (stop song and change song part), I do not see any reason why if you set the “stop song” new setting as “immediate”, the stop button would not react to on-press event… But it probably requires further analysis.
Unfortunately for that, I am afraid I can give a definitive statement: It will never happen… If you don’t want to stop at the end of something (measure, bar, loop whatever) there is absolutely no way the system can determine where to stop.
What I do generally to stop properly something that requires this kind of behavior, is that I play along the last bar, click on “stop” to stop it at the end of the measure (I am always in stop at EOM mode), and then do myself the missing part to finish properly… You can turn this as you want I doubt there could ever be any other way to do it…
Last point is, yes, the split between song and global settings is not logical. And in this particular case this very obvious as we have in the global settings a flag which is clearly related to the song behavior…
My proposal regarding settings management is probably one way to fix this, maybe not the only one nor the better, but I think it’s simple, resilient to system updates and versatile enough to be taken into consideration. Currently it is tagged med-long-term, but the more the system is stabilizing (and it’s clearly doing), the more we need a better config management.