Coloring in Viewpoints is usually not applied just for fancy looks, but as indicators. For example, walls may be colored by type, or by clash results. Rooms may be colored by purpose, or by renter, etc.
It is currently not possible to have this kind of semantic information in BCF. I think an optional Name property on Colors would be a valuable addition.
Additional to this, it would be nice to not only have names for each color, but also one for the entire color schema, to indicate the purpose of the coloring. This purpose would mostly be identical with the purpose of the Viewpoint, which is one more reason why Viewpoints should have names, too.
This request is obviously also for BCF-XML, but I wasn't sure if I should duplicate the issue.
Coloring in Viewpoints is usually not applied just for fancy looks, but as indicators. For example, walls may be colored by type, or by clash results. Rooms may be colored by purpose, or by renter, etc.
It is currently not possible to have this kind of semantic information in BCF. I think an optional Name property on Colors would be a valuable addition.
Additional to this, it would be nice to not only have names for each color, but also one for the entire color schema, to indicate the purpose of the coloring. This purpose would mostly be identical with the purpose of the Viewpoint, which is one more reason why Viewpoints should have names, too.
This request is obviously also for BCF-XML, but I wasn't sure if I should duplicate the issue.