I'm sitting on the fence with this. Yes it could be achieved by allowing stretch planes for each skin or even localised override/editing of skin widths, BUT, I also like to know when I use a particular composite for a wall type or a slab etc that the skins are effectively hard coded so I don't find I have shown 105mm of concrete when it should be 100mm, due to copying attributes or accidental stretching. It is also a lot easier to update drawings when you change a composite as all the elements that use it should change to the latest values. How do you decide when a composite is changed whether an edited skin is updated or retains it's changed width?
Apple iMac macOS Monterey / AC26UKI (most recent builds)
It's the same as the profiles. If you accidentally stretch a modifier in a column profile (not width or height), how do you know it?
2. Copying attributes
When applying a composite "A" to a wall that doesn't already use it, it should get its default thicknesses. When applying the composite "A" to many walls and one of these walls already uses it and has set different thicknesses, you should get a warning "Apply changes to custom thicknesses too". Just like when you have a slab with a custom edge material and change the edge surface. You get a red triangle with a checkbox.
3. Altering composite
When altering a composite that has materials A-B-C and change the thickness of A, you should also get this warning if some element has a different A thickness than the default.
No. In your video, this method works for skin heights. I want to change the thicknesses of it. I know I can add more modifiers to a profile, but profiles do not work with slabs or roofs, because they are not a "lenghty" constuction element that has a specific profile.
When designing a slab, you can have a plan view that's not rectangular (as in most of the cases) and apply a composite like this "Concrete-subfloor-floor". When you use 3 different thicknesses for concrete, 2 for subfloor and 5 for floors, that's a total of 30 different composites. I think we should have all of these in one.