jjs wrote on 19.9.2003 23:38
I was just looking to see about your question, because I have an assembly open and do not have this problem. However, I have colored my parts with the "color" tool and not by defining the material. And my subassemblies look fine.
So to experiment I just opened a part and decided to apply a material... Well, that totally locked up the program! CPU was peaked out and program not responding. So I ended it and started again. Then the same thing happened... But after about 2 minutes it applied the material! Strange... Now I can switch materials normally. Does the program have to to some sort of first run thing the first time materials are used? I think this is the first time I applied them since installing 2004sp0.
Anyway, everything updated fine in the subassembly. What I was wondering was if there was some strange behavior between materials and Edit Color feature, because I vaguely remember having the same problem during the beta process...
You might try to RMB on the subassy in the FM and select the color button on the right. Then select remove color as that would/should remove any setting you may have made in the parent assembly. Sometimes that can cause this behaviour (especially if this is an assembly created before 2004).
Hope that helps!