I see the difference. The 2nd plugin applies and reads attibutes to the component definition. Where as the 1st plugin, uses the component instance. It works fine for edges, faces, groups. But for components, they can't see the attibutes set by the other. Also, I don't know if it matters. But if you are changing the definition of a component, then the change is not unique.

This is a interesting situation. While it seems clear that the company owns the software, can they make a claim for the source code? My guess is yes, but they have to find the fellow (assuming he kept a copy). He probably scrambled the program because of the "sensitive data".

Depending on the extent of the modification required, if very minor, then perhaps a programmer at the level of assembly language might be able to make small changes with debug. I have done it with .com, and .exe files, but don't know about code at the current "state of the art".

@unknownuser said:

http://forums.sketchucation.com/viewtopic.php?f=81&t=30630&hilit=ross+macintosh

Ross has...

Thanks - will hop over there 😉

Thanks again Guys.

I applied a texture to the back of a face in the component where it is never seen, saved the component with the rest of the faces using the default material and now when I import it the material comes with it. If I now change the colour using Component options it works (although the hidden face always stays as the texture I applied directly to it).

However I am still confused, because when I import the component it comes in showing the default material until I drop it in the model when it changes to the texture specified in the component options.

With the original models I did (second sample above) they come in showing the texture specified correctly and they work perfectly when using the component options - AND - there are no hidden textures in them.

Also - with the original models, if I change the colour in component options then re-save the component, when I then import that into a new model it comes in the correct colour and brings that texture with it (the original texture is gone, as expected) - but I did not place any hidden textures in the component before saving it.

Very strange - but at least for the time being I have a solution (until I can work out what I may have done differently the in the original models).

That's it.

Thanks Alz and Jim.

As I said in the heading of my topic - 'I'm getting there' 😉

I also said - 'but need some help.' and you have certainly given me that.

My problem is that I have no experience of programming/scripting, and I am short of time in developing a major project (the scripts for SU are only a part of the project) and have limited time to 'study' something new, particularly something as involved as Ruby - but I will persevere as time allows.

Thanks again for you patience and assistance so far - it has helped no end.

Tig - you are a star.

I could not figure out why one or two scripts ran in the console and others did not.
it seems that by coincidence the 'def name' was the same as the script name for the couple that worked.

Now I understand it from your explanation, it all makes sense.

I have a couple of other questions, but I will put them in new topics rather than take up more of your time here (although if your posting history is anything to go by you will probably chip in there too 😉 )