I created my own File Type Group called "ParRarColors". In this group I added ".rar", ".par", ".par2" for the extensions.
Under Preferences -> Favorites and Recent -> File and Folder Labels. I created a new Label called "ParRarColors" and made the Icon color a Red. I then created a new "Labelled files and folders:" Item with the Label of "ParRarColors" and the Wildcard of "grp:ParRarColors". Everything works as expected, all ".rar", ".par" and ".par2" files icons turn Red.
This is the part that might be a bug:
Back In the File Type Group, I went to add ".r*" so all ".r00" ".r01" files get selected as well... Nothing happens to those icons. So I tested with other extensions like ".sss" or ".000" just for testing... Nothing happens to those icons.
To fix the problem, I had to go to my Labelled Item, Double-click on it so it opens "Edit file or folder color assignment", then just click OK to close. It would then work on my ".r*" and ".sss", ".000" test extensions.
The same goes for if an Icon is already colored Red and I go to my File Type Group "ParRarColors" and removed a working extension like ".rar", the Icons would still be colored Red until I went to the "Edit file or folder color assignment" and closed with OK. it would then refresh the color assignment and take the Red away.
I did Exit out of DO (not just closing) to see if that would help, it never did.
10.0.1.0.4185.x64 on Windows 7
What seems to be happening is that newly added or removed extensions to a File Type Group are not picking up the Labels color assignment.
If this is a bug and gets fixed, great. If not, then maybe this might help someone else realize what might be going on if their Labels aren't working.
The above problem still happens but I just figured a little easier way to do this with the below code as the Labels wildcard code instead of using a File Type Group
Did you literally add .r* to the file-type group? You can't use wildcards there; it has to be the actual extensions.
Including a wildcard chracter in one of the group's extensions may have broken what grp:ParRarColors was expanded into, which may explain things. Just a guess, though.
(Using (.r[1-9]|.p[1-9]|.[1-9]) instead of grp:ParRarColors is fine, though. And if there was no other reason for the group than to define those colours, then it makes more sense to put the wildcard directly in the label and not have the group at all.)
For me it works fine, and doesn't require a restart or even a manual refresh of the file display. A couple of seconds after adding or removing an extension from a file-type group, the file colours are automatically updated.
As you can see, I started out with no wildcards in the File Type Group (which makes sense that it shouldn't work). I then moved on to using wildcards. Then finally just partial extensions.
My install does not auto refresh like yours and wildcards in the File Type Groups, do work(at least they work with Labels). Am I special? Sounds like I might need a reinstall.
No big deal if it isn't (or can't be) fixed. Again, I just want others to know about it. Also just wanted to show you what I see
The video definitely indicates something is wrong, since the actual label appears to be ParRarColors at the top but is shown as grp:ParRarColors in the bottom (not just the wildcard but the label, on the right, starts with "grp:").
Any idea how that happened? As far as I can tell the UI won't let you create such a situation, and label names cannot contain the ':' character at all.
You're right, not sure why the Label has "grp:" in front, I didn't do that. I rebooted and it went a way. Wildcards (.par* etc) in File Type Groups still work like the video showed.