Quote from: gappie on October 16, 2006, 05:10:51 PM
1. i have made custom library field, 'artiesten'. this is the sane as artists, but a list field, so that i can place an album under different artists. now when i make a view with artiesten first grouped and in the second column ungrouped i get artists that have nothing to do with the selected letter in the first column. to make it more clear, here is a pic.
http://www.gappie.nl/fotos/mc12%20a.JPG
the relation between the names at top of the right column and the letter s is that they are sharing the artiesten field with an artist beginning with an s (in this case).
The semantics changed in MC 12 for this usage.
Panes are built from a list of files. After you make a selection, the list of files is filtered. The next pane is then built from this filtered file list.
So if you filter down to files with artiestens starting with "A" and then build a list of artiestens from that file list, you would expect artiestens starting with "A" and also any artiestens in songs with "A" artiestens.
Version 11 tried to change this one special case by not following the flow above. However, this was inconsistent and caused problems with advanced view schemes.
So for v12, we removed the special casing.
I'm really confused. If you look at the example below, how could this be normal or desirable? This change from v11 to v12 really makes using custom-multi-value fields about useless for the way I'm trying to use them. Help!
In this example ArtistList is a multi-semicolon-delmited field. The first pane is set for grouping and the second is not.
So I have C selected, and I'd think that the following pane would only show artists that START with a C, but "Blind Faith" does not start with C and does not even have C any where in the name.
I would think that my C selection would limit all items in the following panes to tracks where the artist name starts with a C. Where did Blind Faith come from?
Is this normal what is shown below? v11 only shows artists starting with C in the 2nd pane.