Hierarchy improvements
Posted: Wed Mar 28, 2018 7:59 pm
Not sure if this is bug/issue or feature request, but I'll do my best to describe it.
The question is around the treatment of custom field in the hierarchy views.
If I select "Hierarchy->New hierarchy", a dropdown is given that lists all fields including custom fields, which are described by their "Title in Muso" together with "Custom x" in brackets. That's fine. However the list of previously used hierarchies just has "by CUSxx" which means you have to remember which custom fields are which numbers - OK if there are only one or two, but not if you are "maxing out Muso" with 8 as I am! Could we possibly have a consistent approach using the descriptive name?
Also, the expansions within the hierarchical view do not seem to work fully with custom fields. The custom field only seems to work at the "top level" of the hierarchy. If it is at the next level down (e.g. by Composer by Instrument, where Instrument is a custom field), then it is not possible to expand a composer in the hierarchical list. Is this a bug or a feature?
Lastly, I note that, when you are at the bottom level in a hierarchical list, all possible internal fields are given as a further drill-down possibility, but not custom fields (perhaps this is related to the issue above).
The question is around the treatment of custom field in the hierarchy views.
If I select "Hierarchy->New hierarchy", a dropdown is given that lists all fields including custom fields, which are described by their "Title in Muso" together with "Custom x" in brackets. That's fine. However the list of previously used hierarchies just has "by CUSxx" which means you have to remember which custom fields are which numbers - OK if there are only one or two, but not if you are "maxing out Muso" with 8 as I am! Could we possibly have a consistent approach using the descriptive name?
Also, the expansions within the hierarchical view do not seem to work fully with custom fields. The custom field only seems to work at the "top level" of the hierarchy. If it is at the next level down (e.g. by Composer by Instrument, where Instrument is a custom field), then it is not possible to expand a composer in the hierarchical list. Is this a bug or a feature?
Lastly, I note that, when you are at the bottom level in a hierarchical list, all possible internal fields are given as a further drill-down possibility, but not custom fields (perhaps this is related to the issue above).