I get them again as before, they worked fine this time. Thanks for the help TIG

Turns out, I think I need to write the texture to disk. The only reason it seemed to work to just take the original filename with the path and assign just the filename was because SU's last file dialog location pointed to where the original texture was. TextureWriter object is the only one that allows me to save out a texture? It doesn't take a Material object as an argument, so would I have to create a temporary object, like a group, assign it the material, export using TextureWriter, then delete dummy object? ...seems messy to me... any better solutions?

@didier bur said: Hi, @unknownuser said: the dialog box says it's in mm In what command ? Please precise what command executes in inches instead of your unit ? I meet the issue too When use "P-P selected faces along their normals " and "P-P selected faces randomly" (projection_V6) It executes in inches instead of MM!!

I.frisken, i think your best bet would be to send adam a PM and see what he says. He always struck me as quite a reasonable chap so he might be able to make you an offer.

/me goes hunting for ninjas

I don't think so, thomthom. Components take colours from layer they are in. And if you select all entities in a layer (with Didier's quick selection plugin), you copy place them in a new layer?

That's a great idea, Bill. I've added it to the feature request list. Cheers,

@thomthom said: Just had another though, if you really want a modal window on mac? Not possible? Not currently possible, unfortunately.

@thomthom said: Can anyone elaborate ... Suppose you have 3 points (p1, p2, p3) and want a point (p4) "normal" to p1. The 3 points define the PLANE and also 2 vectors with origin in p1. If you make a CROSS PRODUCT between those 2 vectors, you will get a 3rd vector that is NORMAL to the PLANE and passing on p1. If you offset p1 using this new vector ... voila! Example: p1 = Geom::Point3d.new(1,2,3) (can be any 3d point, non hard coded) p2 = Geom::Point3d.new(4,5,6) p3 = Geom::Point3d.new(7,8,9) v1=p2-p1 or v1=p1.vector_to(p2) v2=p3-p1 or v2=p1.vector_to(p3) p4 = p1.offset(v1v2) or p4 = p1.offset((p2-p1)(p3-p1)) Regards Marcio

You should be able to calculate the volume, and the maths to work out the weight given the material type and density should be straightforward.

@thomthom said: That's great Dale! Works perfectly. But I would never that expected that .parent would return that. I would have expected that: > group.entities.parent === group > There are a lot of strange things about groups, and that is one of them.

I could only guess so quickly because it's happened to me a couple of times, too!

You need to look in the API methods for various bits... it's all there... Make a list of the loop's vertices. You get a vertex. You get its point in 3D You get the vertex's edges. For the two edges get its other end's vertex and thence its point. You get the vector between the vertex-point and that end-point in turn. You see if vertor1==vertor2 [or its 'reverse']. If they're not 'equal' then it's a corner... .

onViewChange - http://groups.google.com/group/SketchUp-Plugins-Dev/web/Ruby-ViewObserver.html?hl=en azuby

[image: 210y7vd.jpg]

Yes, Gaieus, is very cool, I wish I could use it as soon as possible, but I don't have a project to work in it. best regards

Hello Ross - I don't know. I needed to enable the extension to see it in SU7 Pro, and it went away when I turned it off the Ruby Examples and restarted.

Glad you got it working finally!

Thanks Rick and Jim that helped!

I see. I never looked that that class yet. I just saw the UI::Menu class and thought that was the one. And there was nothing on the constants there. It says that UI.Command is the preferred way to add toolbars and menu items, but why? what's the difference and benefit?