Thanksdamian wrote:Good Morning @eivindkv:
Thank you for 4.000 lines and 49 files of code. Incredible!
No, the matter in a solid consists of a single material. However, this is described by a list of materials. The difference between the composition and the stack is the way how the look-up of its properties is done.1º) will the MaterialComposition have layers?
For a composition, the look-up is started at the top of the stack, and the first match is returned. This makes it possible to override sub-sets of a material by stacking another on top. E.g if you read the post by bernd, he would like to have concrete with different values for YoungsModulus. This is possible by having a "standard" concrete at the bottom of the stack, and then different materials with only one property (or a few), YoungsModulus, that differentiates one type of concrete from another.
For surfaces, think of the stack as a bunch of physical layers. When searching for a property, you must first specify the layer in which to do the look-up. As an example, think of an object with a background color and a silk-print on top. One layer would then specify the background color, and the second one could specify a transparent texture that would be put on top. This is how I envision it; it is not implemented yet
Each solid is a MaterialComposition object, and the Material property contains an array of solids to cover compsolids.2º) could a solid have a MaterialComposition? The question is with a single solid, no with a compsolids.
This could be specified as a property, but would not easily be reflected in the geometric model.3º) how will the thickness of every layer be specified?