Ah, I can see the problem with this part indeed. In gray it looks ok but in any other color it seems wrong to me. The knights helmet probably should be hardcoded gray (maybe even the whole 'torso shape' it's mounted on should be hc gray).
The black lines disappearing when used in black is a problem all non 100% c16 parts have, so I don't think you could 'burden' the part authors with making all patterns hardcoded (inflating filecount dramatically).
Maybe we should only specify a set of rules on how to determine what part of a pattern is declared 'transparent', e.g.
1. Compare different colored real life parts. (the current way I'm guessing)
2. If there are non, take a 'vote' on this in the pt; or let the pt admin decide; or wait for TLG to come up with a 2nd colored part.
Or if the clear section is really ambiguous, release a hardcoded (temporary) part and replace it in a next release with a 'moved to'. This is the backwards compatible way of doing things, but it would clutter the library though. And personally I'm not a big fan of 'coloured' parts in general.
The black lines disappearing when used in black is a problem all non 100% c16 parts have, so I don't think you could 'burden' the part authors with making all patterns hardcoded (inflating filecount dramatically).
Maybe we should only specify a set of rules on how to determine what part of a pattern is declared 'transparent', e.g.
1. Compare different colored real life parts. (the current way I'm guessing)
2. If there are non, take a 'vote' on this in the pt; or let the pt admin decide; or wait for TLG to come up with a 2nd colored part.
Or if the clear section is really ambiguous, release a hardcoded (temporary) part and replace it in a next release with a 'moved to'. This is the backwards compatible way of doing things, but it would clutter the library though. And personally I'm not a big fan of 'coloured' parts in general.