Scratch-gui: Prevent accidentally losing trim operation in sound editor

[ericrosenbaum]

Expected Behavior

It should be clear how to accept a trim operation, and we should try to prevent the error in which people use the trim feature but don't realize that it will not be saved unless they press the "save" button.

Actual Behavior

We see people adjusting the trim until it sounds right, and then navigating away from the sound editor (which causes the trim to be lost).

We should consider:

• Automatically accepting a trim operation that has not been saved when you navigate away from the current sound in the editor (by switching to another sound or by switching tabs)
• Some other way to make the workflow clearer. For example, the trim button could bring up a modal like the "record" modal, but only for trimming.

cc @carljbowman @paulkaplan

[hedgehog125]

Maybe the other buttons could deactivate while you edit it and there could be a green tick and a red cross to confirm and cancel?

[hedgehog125]

On the record modal there could be a tooltip on the x and it could say something like "cancel"? Or, when you click the x it could confirm if you really want to delete it or not.

[Kenny2github]

Perhaps a confirmation when switching away? Like "are you sure you want to leave? you haven't finished the trim yet!"

[kyleplo]

@Kenny2github

[paulkaplan]

Trim no longer exists, closing!