You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
We've just discussed this a bit in the group call.
Can you provide some more information, like why could this not be written in the BCF issue itself or a comment referencing the viewpoint?
... like why could this not be written in the BCF issue itself
Because coloring is a property of a viewpoint, not an issue, obviously.
... or a comment referencing the viewpoint?
Comments are your answer to everything, aren't they? :P
Yeah, I could put a kind of "color legend" into a comment, sure. That would suck, though.
A comment is just unstructured text, how would I (or anyone) parse it to get the color names back?
Which I think would be a valuable thing, or are you going to tell me that our software is the only one that has named materials and named colors, e.g. for indicating different check states?
Activity
GeorgDangl commentedon Aug 25, 2025
Hey @an-ho, thank you for the issue!
We've just discussed this a bit in the group call.
Can you provide some more information, like why could this not be written in the BCF issue itself or a comment referencing the viewpoint?
an-ho commentedon Aug 26, 2025
Because coloring is a property of a viewpoint, not an issue, obviously.
Comments are your answer to everything, aren't they? :P
Yeah, I could put a kind of "color legend" into a comment, sure. That would suck, though.
A comment is just unstructured text, how would I (or anyone) parse it to get the color names back?
Which I think would be a valuable thing, or are you going to tell me that our software is the only one that has named materials and named colors, e.g. for indicating different check states?