01-28-2020, 02:54 AM
Let's talk about how this would be realized in the UI. Should I change it so that you have to click a save button to actually commit the changes, and they are all temporary otherwise? Should that be the default behavior or should it be something you have to enable? I think having to click a save button not to lose changes might be tedious for most users when they aren't in a situation like what you are describing, so is it better to toggle something on that indicates you want the changes to only be temporary? Should there be a checkbox or switch on the dialog that says something like, "automatically save changes" that is normally checked by default, but if you uncheck it, a save button is displayed? Or should there be a "revert" button that will revert all of the changes back to what they were when the song was first loaded? I think I would have a snapshot of the text display settings that were present when the app was first loaded, and that's what I would revert to. That means those saved settings would only be updated the next time the application is closed and reloaded. That certainly would be the easiest implementation.
Let me know what approach you guys think you would prefer, or if you have other ideas, please share them.
Thanks,
Mike
Let me know what approach you guys think you would prefer, or if you have other ideas, please share them.
Thanks,
Mike