Multiple Instances (Encouraging Feature Development:)

[Oliviander]

Hi Simon,
your clue [THX again] is working but with a limitation
as I told you my exanple was a simplification
therefore I have some more ALBUM_Categories
and some Albums have two exisiting entries.
In such a case they would get a zero as a TagValue
for any searchpath and would therefore would be hidden.
im any path.

I am aware that I can circumvent this by reversing the
the process:
Setting the TagValue to zero for all Tags and all Tracks used this way.
Then deleting the Tag for all matches of the Tracks.

But to do that I have to set the TagValue of the used Tags
to zero for all tracks in the beginning.

I haven't tried it but I if I am understanding your manual right.
you can't just add a tag for all tracks in the tagUpdatefile
without using a match condition.

Therefore I should have at least one Tag in my collection,
that has the same value for all tracks.

In the Moment I haven't any but before adding one to all my tracks
maybe you have an idea how I can trick MinimS to do it
without that need for such a nonsense tagvalue in my collection.

--> This would not be needed if there was a modified replace
TagValue function as suggested.

Thinking about that I have another questionable idea:
Minimserver could add an internal tag to the tracks
it's value simply displaying the source (the contentDir) value
(either in cleartext or simply an increasing number for the lines)
when reading the files. By using this value as a condition
I could even better bend the limits.