rrfpacker wrote:Does it seem weird that if I want to create an Album Rating node such as the one I want to create, I can't keep it with the other Album Rating nodes in MN? Is that the behaviour (the behaviour being that if I want to use a collection as a filter the node goes in that collection) that works best for MN?
I am not sure that understand what you want. The default Album Rating group is under the Magic Nodes folder. You created a new node and decided to put it into some collection, so you got that node in the new Album Rating group under that collection. You could create several groups with the same name under different parent folders and I cannot see why such behavior is weird to you. I think it would be weird if it is opposite, i.e. after I assign a collection to one node from some group, if all other nodes from the same group move to that collection. Not only that it would be weird, but in that case there would not be a possibility to have several groups (or nodes) with the same name under different parents. However, if you want to move all nodes from the default Album Rating group from Magic Nodes to some collection, then you need to assign the same collection to all those nodes.
If you complain about the fact that using some filter with some node automatically assign that node to the corresponding collection, then you should know that such behavior is introduced with MM4. In MM3 you had a possibility to assign different MM filters to the Magic nodes wherever they are, in Magic Nodes folder, in Library, even in Playlists folder, but with MM4 you cannot have node with the filter of one collection outside of that collection. It would be totally weird if, for example, I have node with the Video filter placed into the Music collection, don't you think?
However, there is always a possibility to use some filter even for Magic nodes outside of the corresponding collection of that filter. Here is the short guide:
- open the Options dialog box, choose Magic Nodes sheet and turn on the "Allow editing of SQL queries" and "when select a field node" options;
- make some simple Magic node which is placed into the collection whose filter you want to use, e.g. for the Music collection it could be Test|Child of:Library|Position:First child|MM filter:Music
- expand that collection and select that new node -> you would get the Magic Nodes SQL Editor dialog box displaying the filter of that collection, e.g. for the Music collection it would be WHERE ( Songs.TrackType in (0,4) )
- you should copy part of that expression after WHERE (in this case it is Songs.TrackType in (0,4)) and use it in your Magic Nodes masks in the Filter qualifier, not matter what is the selected collection of those masks.
By the way, if you want to know what I am talking about, it is recommended that you read the PDF manual whose link you could find in the first post of this thread. It is obsolete, but still useful for understanding of the Magic Nodes mask's syntax.