05-15-2024, 04:33 AM
It just requires a lot of database changes, UI changes, and this has to occur on all three platforms as well as the companion app. So unless there is strong support for an additional metadata field, I'd prefer not to change all that. If more users chime in that they would get value out of a subtitle field, then I can plan it for one of the future updates. Additional fields also don't come for free - even if the field is blank, when querying for the data for the entire library, it's another field that has to be retrieved per song which has an impact with very large libraries in terms of load times and memory allocations.
As far as the ability to rename labels, I planned for that with the Custom Group field, but it requires going through every UI in the entire application that can reference the field and adding code to populate the label instead of being able to statically define it in the UI layout. So it's not that it can't be done - it's just that I haven't had time to add code to support that. I do plan on allowing more fields to be renamed in the future. Having said that, it does create potential confusion and difficulty when trying to assist users if they've renamed a bunch of fields and I don't know what those fields map to.
Mike
As far as the ability to rename labels, I planned for that with the Custom Group field, but it requires going through every UI in the entire application that can reference the field and adding code to populate the label instead of being able to statically define it in the UI layout. So it's not that it can't be done - it's just that I haven't had time to add code to support that. I do plan on allowing more fields to be renamed in the future. Having said that, it does create potential confusion and difficulty when trying to assist users if they've renamed a bunch of fields and I don't know what those fields map to.
Mike