I hope you found PathCopy in the list

It is possible to "construct" the shadows (as semitransparent faces) with Ruby, but with great tools like LightUp and Podium that work with SU, I don't think you'll see anything soon (though I could be wrong).

Sounds like a candidate for SKX

@adamb said:

I end up having to do:

mask = (mask or object.getmask)

But now you know you can use

mask = mask || object.getmask

It saves typing the parentheses... (FWIW)

I could look into extending weld. I will add it to my list.

I've started one, but it's not ready for release yet. I may have to bump its priority. The challenge is nested G/C's...

@tig said:

You can also do it without Ruby...
Try this way...
In the model select the component instances you want to be replaced - either by manually picking them (in which case they can even be a mixture of several types) OR by using the Component Browser (model-tab) and then right-clicking over the definition's icon that you want to have selected and pick 'Select Instances' - that way all of its active instances are selected.
Now use the Component Browser - either in the model-tab to use components that are already within the model, or from any other 'external' location for components that are currently not yet loaded into the project - again you right-click over the definition's icon that you want 'to add' and pick 'Replace Selected'.
Now the components you selected have been replaced by the component you wanted...

It's possible to script it BUT it might be as easy to do it this way... There are already several component swapping scripts too...

It can be done using the Component Browser, but when you have lots of components, it can be easier to select a desired component on-screen rather than hunting through the browser. Though I wrote ApplyTo before the Component Browser offered that functionality, it retains its relevance for this reason.

You could try offset.rb

While I wrote it to provide standard "flat" offset capability, I noticed it does perform 3d offsets. It may not be exactly what you want, but it could form the basis for a 3d offset.

SceneExporter and SceneExporterPro will do this as well.

@thomthom said:

@rickw said:

(which will be increasing by one in November)

Congrats man!

Thanks! It was quite unexpected, but also very welcome.

@chris fullmer said:

That's why Rick has been so quiet lately - he's been locked down in his basement for the last 6 months deciphering image formats. Way to go Rick!

Chris

LOL - you're not too far off. Between heavy (and sometimes overlapping) deadlines at my day job, literally being in my basement deciphering the PNG format (and hopefully soon the inflate/deflate algorithm), and trying not to neglect my family (which will be increasing by one in November), I've been rather quiet here.

Oh, and next week, I'll be at the Google I/O conference with Todd. If anyone else is attending, stop by our Developer Sandbox booth and say "hi"!

Chris,

If BTM has certain of my scripts installed, he will have array_to.rb which adds methods .to_i and .to_f to the Array class to convert all members to integers or floats. That could be why array.to_i worked for him and not for you.

Related to work on ImageProfile2 (oops, spilled the beans), I have deciphered the PNG spec and can now read the PNG image data in Ruby (unfortunately, it is PC only until I also decipher the deflate/inflate algorithm).

While that may seem off-topic, it does have a direct correlation - an earlier thread discussed the possibility of a Ruby to create bump maps from SketchUp models (which I'm working on when I can). But it is conceivable that with some work, I could create a Ruby to turn a bump map texture into real geometry, just like this thread requests.

Just a guess (no time to try it), but 90 & 45 could be the framing member size (90mm is about 3.5 inches, 45mm is about 1.75 inches, or a "metric 2x4"). I have a friend looking into it. I agree that it's probably the character set causing the problems.

Without doing some investigation into the available Layer methods, I'll go out on a limb and say it's possible. Just need to find time

The way I understand it, applying a change will trigger another check within SU to see if anything in the model has changed. This will supersede any previous checks (and thus any previous observer calls). You should store any planned changes (i.e. transforms) and the entities to be changed, and call them after everything else you want to check is done.

You're lucky you haven't gotten a BugSplat - that was what happened when I did some early Observer experiments in this vein and figured out what was happening.

@baz said:

@unknownuser said:

Have you looked into Organizer?

Thanks Rick, tho it seems a bit complicated for my poor brain. I can see myself getting in lots of trouble trying to organise subfolders, especially considering the apparent dependency of various rubies on each other.
baz

Two things:

1. Organizer can do a simple test and notify you if you move any required files, letting you know you need to put them back in the Plugins folder. Also, creating a backup of your Plugins folder prior to using Organizer can save you some headaches.

2. I do offer support for all my scripts, so if you have questions, just ask

It is impossible with dimension objects, but possible with other methods.

My MacBook has Xcode or something like that (I'm not a "Mac person" - I just got one for self-preservation for dual-platform SU ruby development ). It's color coded and has auto-completion capabilities as you type.

Also, you can use "unless" instead of "if not", and a bit of restructuring gives you

unless file_loaded?(__FILE__)
   file_loaded(__FILE__)
   #do your stuff here
end

Though it's not a big deal, it eliminates any unnecessary calls to file_loaded()