it would be very nice if such BRUSH is a bit smart to subdivide the surface automatically when it moves over it and is displacing it... by now i must subdivide it by myself...

It is possible BUT I'm too busy to think at the moment...

Well that's good to know (I won't try to cobble together a test then). On a side note, even with the cut/paste option, I'd still have to have the Outliner open and dig through the tree. The Layer Manager script does a good job at letting you r-click and quickly move contents

Oops, sorry, I'm not used to looking at the user info for OS data - it clearly states "Vista" as your OS That's a really strange situation. Contact me via Smustard and we'll go from there.

Well, sorry for replicating an already known bug... on the upside, now I fixed the same bug in my own code. Thanks Todd!

Organizer script from Smustard can help you sort the scripts. IIRC there are one or two other scripts that does more-or-less the same thing, but I don't remember what they are called. I'm sure a look-see in the Ruby Script Index could help out as scripts are usually called something logical and easily recognisable if you know what function (-s) you require.

or you can get it from the source (me.)

I've noticed it, and I think it's an issue with ruby in SU - creating a lot of new geometry in an already dense model takes a LONG TIME. However, I'll check the code for Windowizer to see if there's something in it that might be a culprit.

but I STILL like the eplanation for hexadecimal... I always saw that on my calculators and wondered 'what in the world is that?'

@lapx said: Look up k-tools ruby. Under geometry/ round edge. It will do what you are asking. Sorry to be slow today, under my K_tools 5, I don't have the option of rounded corners, Angle division, outer circle of triangle, inner circle of triangle, Make T, Make L. However, thanks for the help. Ken

Good idea Coen . will this be something like the scriptspot blog? See here: http://www.scriptspot.com/

Most of the code is trivial, only soft selection would have to be coded from start since the smoove is closed-source. But I cant devote any time to this at the moment. We should spread the coders' group by not delivering on-demand. Once u start, the simplicity of ruby Api is addictive.

The puppet tool would be nic but you can get close by combining suanimate which is available @ ohyeahcad, the people who make podium. Combine this with ffd and you can do a lot of what you desire. Making it easy with a visual tool should be possible using these two scripts that are already developed.

Sure you could use grep, sed etc but wait, what if we had a scripting language in Sketchup that had good file reading capability, powerful regular expression matching, and a binding to the Sketchup geometry API etc. I guess we can only hope. Seriously, something like this works fine: IO.foreach("my_inputfile.ext") { |aline| /^(\S*) ([^$]*)/.match(aline) verb = $1 rest = $2 case verb ....whatever you need to do here eg entities.add_face, entities.add_group etc } This is my mickey mouse .obj importer I use for Sketchup: pos = [] tex = [] group = nil IO.foreach("/tmp/test.obj") { |aline| /^(\S*) ([^$]*)/.match(aline) verb = $1 rest = $2 case verb when "s" # ignore smoothing group when "v" # close current group if group pos = [] tex = [] group = nil end / (\S*) (\S*) (\S*)/.match(rest) pos.push Geom;;Point3d.new($1.to_f,$2.to_f,$3.to_f) when "f" if /(\S*)\/(\S*) (\S*)\/(\S*) (\S*)\/(\S*)/.match(rest) vertices = [pos[$1.to_i], pos[$3.to_i], pos[$5.to_i]] elsif /(\S*) (\S*) (\S*)/.match(rest) vertices = [pos[$1.to_i], pos[$2.to_i], pos[$3.to_i]] end group.entities.add_face vertices when "g" # open a new group /(\S*)/.match(rest) group = Sketchup.active_model.entities.add_group group.name = $1 puts "group(#{$1})" end } Adam

It has also been helpful when using the 3DS export filter (been experimenting with using it for passing my files to a Lightwave user as it will do somethings better than the Lightwave Plugin version 006).

Too bad. Thanks for the quick reply, Jim. Do I assume that this has been put on "the wishlist" at one time or another?

@Todd You forgot the scripts programmed as extensions. Their stub is loaded every time Sketchup starts, but the rest is loaded depending on the checkbox status in Preferences dialog. And this status can't be reached with Ruby. But it would be possible to overwrite the methods "load" and "require' to get to know which files get loaded. You only need to make sure the overwriting is in the script loaded first from Sketchup. azuby

Be advised that execute_script is very buggy on Mac. It will mangle the string sent if it contains ";" or "," and probably other chars as well. Also "document." doesnt work.

Edison, I think I may a have a workaround for you. I am certainly not an expert at dealing with contours, but through recent experimentation and the availabilty of newer scripts this could be what you need. You'll will need to check the accuracy of the "re-segmented" contours, however, to see if they are within the tolerances/lever of accuracy you want. See the attached .skp for a mini-tutorial. You will need the Weld.rbby Rick Wilson and the BezierSpline script setby Fred06. If you plan to create a terrain from the contours, then I would suggest TIG's Hidden2Layer.rb (version 1.2) script and use it as mentioned here: http://www.sketchucation.com/forums/scf/viewtopic.php?f=57&t=8726 . In summary, the procedure is this: A. Import the contours. B. Triple click on a contour of segments and WELD. C. Then right click on it and choose the the BZ context option of PolyLine Divider. Do note that for some reason (I think it has to do with the number of segments), the BZ context options may not be available; in that situation then bisect the weld segments into smaller lengths (see the mini-tutorial, Step 2). D. After completing Step 3, then you may want to weld the "segment-reduced" contour path back together into one continuous polyline.[image: Fygv_BZContextMenu.jpg]Mini-Tutorial for BZ method of segment reduction UPDATE: If Weld.rb does not work on all segments of a contour, try a selecting a smaller set of segments. OR, try selecting a few contour elevations (use one of SU's side views to do this), copy and paste them into a new file (or create a component out of them and then do a context menu Save As to create separate .skp), then try to weld, etc., then repeat the process for another set of contours; finally paste these back into one file. Otherwise, have the segments simplified by the surveyor in AutoCad first, or have them subdivide the one DWG file into 4 or more subfiles.

I'll add this this evening. Thanks. Todd