03-14-2023, 09:54 AM
Any or All would result in the same thing, but with the current implementation, it's more efficient to have nothing selected (Any) so that MobileSheets just ignores the field when processing all of the songs versus checking each song to see if one of their values matches the list of every value in the application. I don't have specific optimizations to detect when the user selected everything and to ignore the field in that case, because that involves more code, and also creates issues when the user adds new fields - just because the user selected all values before, does not mean that MobileSheets automatically selects any new fields that are added in the library. That's what the "Any" selection means. I don't really want to change all this behavior and potentially introduce unexpected bugs. So I'll just change the wording for the collection field to match the others and I won't be changing the logic. There is no reason to "Select All" if you just want MobileSheets to use every value - select nothing in that case. The reason for the "Select All" is if you want to select all initially but then uncheck a few specific values. Alternatively, you could just select those values and then select "Exclude" as the mode.
Mike
Mike