[Zubersoft]

It seems like the consensus is to not save the tempo changes in the metronome window, so I will modify the code for this. At a later date, I may implement some of the suggested changes, such as having a separate entry in the database for the metronome, and providing a button to synchronize/save changes between the song tempo and the metronome tempo. Note that I do allow multiple tempos to be added to the metronome, so at the very least, if a new tempo is added I have to save it in the song. Then if the user changes that tempo value, changes wouldn't be saved, which might be odd. I don't want to add complex workaround logic for this, so the user would have to go into the song later and fix the additional tempos. The other option that comes to mind is to add a save button next to the tempo field (to the left of the tap to set tempo button) that would write the tempos to the song. This would then require me not modifying the database or song in any way when multiple tempos are added and only saving them if the user taps the tempo. The problem with this is I'm currently using the song's tempo list to store these values, so I would need to separate that out. Do you guys have any thoughts on this? Obviously the simplest thing is just not to save the tempo changes at all, but then you wind up with that weird problem when adding additional tempos in the metronome dialog.

Thanks,
Mike