07-05-2019, 07:40 AM
That will do it. I will add logic to account for that and ignore it.
I have also discovered a few ways to reproduce the problem with TextDisplaySettings being left in the database. If you edit a song using a chord pro file, remove the file and replace it with a blank page or PDF, the text display settings will be left in the database. Likewise, if you use the swap file feature to replace a text or chord pro file with an image or PDF, the text display settings will be left behind. I am going to work on fixing all of these scenarios that result in entries being left in the database. I haven't thought of any other scenarios yet, but I probably should test with the companion application as well to verify no entries are left behind when using that.
Thanks,
Mike
I have also discovered a few ways to reproduce the problem with TextDisplaySettings being left in the database. If you edit a song using a chord pro file, remove the file and replace it with a blank page or PDF, the text display settings will be left in the database. Likewise, if you use the swap file feature to replace a text or chord pro file with an image or PDF, the text display settings will be left behind. I am going to work on fixing all of these scenarios that result in entries being left in the database. I haven't thought of any other scenarios yet, but I probably should test with the companion application as well to verify no entries are left behind when using that.
Thanks,
Mike