With the SU API it's possible to select items inside groups/components. It's just the SU UI that doesn't do it.

Hey thats great! Cheers!

Nope, nothing that is open in the API or anywhere that I know of. Maybe some of the more serious "hackers" would be able to figure it out, but its not availabe through the API. Chris

Yeah, the toolbar Fredo has come up with is amazing. Makes me wish all the coders would collaborate and jointly work on perfecting some of the "must have" tools. Could you imagine how good sculpt tools, shape bender or some of the others would be if it incorporated Fredo's toolbar? As far as a shape tiler ruby goes, I guess the most challenging part of that coding would be fitting the tiled shapes into a defined space and having the edges cut off accurately. It's interesting how LWCAD does it. If you see this video - http://www.wtools3d.com/swf/online_help/LWCAD_30/detailed_sidewalks/detailed_sidewalks.htm It's amazing how you can turn the array of tiled shapes as if it were a texture and have it still fit within the face. I think a ruby like this would have to start maybe as a hatch tool of some kind, and then have the script fill every face in the hatch with the chosen shape. How would you guys perceive a tool like this functioning?

We've got such a method in the SKX library. That reminds me; I've been meaning to get a first release for SKX out for the stable methods we got.

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).

@gjenio said: Maybe I don't get your request... but Sketchup can already do dimensions like that! What's the problem? I understand,but to do this taking many time,need draw construction lines? I want it looks like cline tool or something!I need distance between model and dimensions without using construction lines. My english is not so good to explain punctually!

I'm using Vray and it has an option that overrides all materials and make them the same. However transparent materials also gets opaque so thats why I wrote this plugin.

Infinitely extending xlines can't become lines [edges] - they need a start and an end. 'Short' xlines can become lines [edges] as they have a length... Project2 has 'short' options for some xline operations...

Undrop multiple Funny things (click image) [image: QrQi_Piltigthom.jpg]

诞!

Thanks for the reply, TIG. I did try your script over night and yes, it is quite different!!!! Thanks; i think it will be a handy addition..... I love this place.

I moved all of my development files out of Plugins yesterday. With the exception of the updated file, it is the same os the online version. But here it is again just in case. protrude.zip

Thanks TBD, so your temp folder is called "TMPDIR"

Here is a shot of the functionality I am working on. This would allow a practically infinite number of scenes which will be expanded and collapsed in the normal way (not yet shown) based on the scene on the focus line. [image: 6yLK_Sceneexpand-collapse.png] This part is easy but how to make collections or groups of scenes, as with components, requires some time to work through necessary amendments to the interface, together with SU display/ web dialog interaction. I am working on these*. @chris fullmer said: An extra row of scene tabs is not possible through ruby. But it would be possible to make an entirely new scene manager through webdialogs that could be organized an possible way. But Webdialogs seem to give everyone lots of headaches because they work differently on Macs and PC's. Chris Don't think about this unless you use a Mac. Anyway it will be solved; maybe not here. By the way, how many members actually use a Mac? A useful statistic for the politicians among us I think. Keep in touch Chris edit *See this topic

Dammit, I came to this thread via another and didn't notice it was a year old. I guess this project died out then.

thanks Chris, I PM'd you earlier with some ideas actually!!!

I agree - more times than not you should model on Layer0, then put the collection of bits as groups/component-instances on different layers... This method let's you change the current layer BUT be careful to keep your raw geometry on Layer0...

Cool indeed this new plug! Bravo!