Since stickers and patterns are allowed to use RGB colors, it seems to me that only the special colors (like this metalic one) would need LDConfig.ldr treatment, and I wouldn't expect there to be all that many special ones.
One known bug in LDView is that all !COLOUR commands are global to the entire model. (I believe that the last one loaded "wins".) This obviously shouldn't be a reason to avoid using !COLOUR in sub-files, but it is something to be aware of, since the potential for conflicts goes way up. However, if we decide to go this route, I'd want to know about it before releasing LDView 4.2, since it's definitely something I'd have to then fix. I haven't fixed it before now due to the fact that nobody has ever noticed that it's broken in the first place, so it just didn't get high enough on my priority list. (The fix isn't exactly trivial, since I have to add fully scoped color tracking, where now I have a single global color palette.)
One known bug in LDView is that all !COLOUR commands are global to the entire model. (I believe that the last one loaded "wins".) This obviously shouldn't be a reason to avoid using !COLOUR in sub-files, but it is something to be aware of, since the potential for conflicts goes way up. However, if we decide to go this route, I'd want to know about it before releasing LDView 4.2, since it's definitely something I'd have to then fix. I haven't fixed it before now due to the fact that nobody has ever noticed that it's broken in the first place, so it just didn't get high enough on my priority list. (The fix isn't exactly trivial, since I have to add fully scoped color tracking, where now I have a single global color palette.)