Hello James,
You wrote:
"Secondly, and more specific to your roller example, you can use a
pattern to create the 65 instances of your roller. Now when you change
the material properties of one member of the pattern, the other 64
should follow."
Now, that would be true if I was a roller bearing designer, but I'm not. I just import this kind of parts say from TraceParts, and then need to assign a material to all it's sub components so I can calculate the mass of my whole design. Spaceclaim does not output any mass unless all of the components selected have a material assigned to them. Given Spaceclaim was meant to modify models rather than create them, I'd just like to see a simple way to do this fast.
It seems there are already differences between the current and the previous release, where the solids, not the components needed to be selected. That appears to have improved after the update.
As for cascading down: Yes, I think that would help at times, maybe as an option. When I assign a material, it would cascade down the whole branch on request, and when I move a part out of the component, I think I would expect the material to stick to the part. Cascade-assigning a new material to the next higher level would then probably overwrite all below, that would probabbly not surprise me. In such cases, we could still not use the cascade option.
Regards,
Martin