Yesterday, 08:50 AM
With how many settings you are talking about, I think I would prefer to place it all on a fullscreen UI that is completely separate from the existing dialog, and I imagine most users would configure defaults for it that wouldn't need to be overriden per song. So I would create a new database table for these new advanced settings that wouldn't be populated per song by default unless the user checks a box to override the defaults. That way I'm not storing tons of data in the database that is rarely if ever used.
When it comes to custom fonts, it's a little bit of a can of worms if I let users provide their own fonts, as then I have to store that font as part of the library so it's included in backups, exports, etc, otherwise it won't load properly on other devices. Or I could take an entirely new approach to it and have a different part of the settings where users can import fonts, and this would only be stored on the current device, and users would have to install those fonts on their other devices in order to view the chord pro file with those fonts. This doesn't work well at all with my current way of handling fonts, but I'd have to adjust things to account for it. If I just add support for that font you provided, that's not as big of a deal, although it still requires quite a few changes.
When it comes to ABC sections, I'll revisit that when/if I can integrate abc2svg, and then see what is required to feed it custom fonts, because I imagine things are going to get weird with the embedded javascript engine when it comes to accessing local files.
As far as the Microsoft Store, version 3.9.0 was available since like Wednesday I think. I'm not sure why you are unable to update, because the Microsoft Store certainly shows that it is available.
Mike
When it comes to custom fonts, it's a little bit of a can of worms if I let users provide their own fonts, as then I have to store that font as part of the library so it's included in backups, exports, etc, otherwise it won't load properly on other devices. Or I could take an entirely new approach to it and have a different part of the settings where users can import fonts, and this would only be stored on the current device, and users would have to install those fonts on their other devices in order to view the chord pro file with those fonts. This doesn't work well at all with my current way of handling fonts, but I'd have to adjust things to account for it. If I just add support for that font you provided, that's not as big of a deal, although it still requires quite a few changes.
When it comes to ABC sections, I'll revisit that when/if I can integrate abc2svg, and then see what is required to feed it custom fonts, because I imagine things are going to get weird with the embedded javascript engine when it comes to accessing local files.
As far as the Microsoft Store, version 3.9.0 was available since like Wednesday I think. I'm not sure why you are unable to update, because the Microsoft Store certainly shows that it is available.
Mike