(You could look it up in the above list). I found only a couple of times something with "layer", and no method to set/change visibility of a layer. I suppose all the layer methods (like many others) are up to now only empty place holders. In addition to that, it depends on what features can be read from the .dae model. As we know, SketchUp's .dae exporter doesn't preserve scenes and layers (but on the SketchUp Showcase they have scenes!). Similarly, the Pompidou Viewer also contains methods for handling geometric primitives and materials (edges etc.) but models are up to now only loaded as a big mesh object, without distinction into single entities.

@unknownuser said: ... would Sketchup.send_action("fixNonPlanarFaces:") do anything in this case? ... I should've saved the file with the messed up face to try it on! I ended up with something similar to TIG's suggestion,except that I found any vertices referenced more than two edges on the same face. Then I was able to re-create the faces using the original face's vertices. -- Karen

num = ENV['NUMBER_OF_PROCESSORS'].to_i is much easier than the other way and should be fine unless you want to have a cross-platform solution... We don't know if MAC has the same ENV variable 0 - some references are similar to PC, while others can be the same ??

That is a much more efficient way of doing it [transforming [or erasing] entities en mass is often preferable]... But in my defense... the title of the post is move **vertex**... NOT move **vertices**... - so there is probably no significant benefit in the en mass way when he's moving just one or two or three vertices - obviously if a whole load of things are changing a time lag will be noticeable...

Get's the ComponentDefinition of the ComponentInstance or Group definition = self.get_definition(entity) Get's the bounds of the definition - note that if you get the bounds of the instance it will be a Boundingbox aligned to the model axis - not the instance axis. Which is why you need to get the definition bounds. bb = definition.bounds Now transform the points of the definition boundingbox with the transformation of the instance. pts = self.bound_points(bb).map { |pt| pt.transform( entity.transformation ) In other words, get the boundingbox of the definition and apply the instance transformation to the coordinates of that boundingbox.

Unfortunately there is no control over the amount of lens shift in SketchUp. There is currently just 2pt perspective - as mentioned, not even that can be controlled reliably.

Thanks sdmitch - The Updated Code Snippet does everything I wanted to achieve and it is now being used by members of the IMVU-SketchUp Community to "Antagonize/Annoy" some of those unfortunate people who mistakenly think only AutoDesk can produce 3D Model Making Software.

[encourage] [/encourage]

@unknownuser said: @Jim I must say that I am bluffed with the speed of Ruby, thinking that all the lines are interpreted and that I use many Array operations which have a lot of code behind them.[/qoute] My thought is that it is fast because there are no objects being created. The arrays being manipulated contain only pointers to integers which there is only a single instance of in Ruby. @unknownuser said: PS: another challenge would be to create a Sudoku solution workbench in Ruby! Yes, that's a good one; and i had a similar one in mind called the "100 squares" puzzle.

OK.. so, for those you who have read the thread.. looked at the template, and scratch your head and wonder why all the complexity to control a private array ?? Answer.. it's just an example, of a private library mixin module. In practice, you can rename the mixin module to whatever you like... and insert whatever proprietary functionality you wish to include in only YOUR plugins (ie, methods in the mixin sections, other class variables and constants, etc.) whilst not allowing some other "hack" to use those features in their plugins.

@arcad-uk said: So why not grab a copy of the earlier version while you can... http://support.google.com/sketchup/bin/answer.py?hl=en&answer=60107 import through the earlier version then bring it into v8? 1+ - I got SU7 and the importer plugin on disk archived.

Ok thank you Dan. I will try that.

thank you very much Thomas and Tig that prompt reply! I will try to implement your suggestions right now

By 'hand built' I mean 'made manually', i.e. without using any code... that's all... If you make a group that straddles the origin, then its origin [axes] are located at its bounds.min... As I tried to explain... you can then move that group from its insertion_point back to the model ORIGIN, and then apply the same translation transformation BUT as an 'inverse', to the group's entities... so that it appears in the same place in the model, BUT its actual axes have been relocated to the ORIGIN...

Not that i know of....

Thanks Dan, Your suggestion to write callback that is called from killing object, was very useful idea - and makes nice readable code. Much better idea then various signals I planned to use before. Thanks again, Marija

@dan rathbun said: obj.respond_to?(:activate) Thanks Dan, description - sure will help. Edited: Previously, I used obj.methods.include?(someMethod). - That will give an error if the object wouldn't be a class, nor module. But using respond_to? will work on any selected object without errors. Jst true or false I was wrong in blue words. Actually, .methods can be implemented in any object. 134.methods, nil.methods, "dsfg".methods, false.methods, Class.methods will always work.

So assuming you want some data encapsulated within the script file itself, that will use it. A Here Doc, or Array or Hash, would seem to be a much easier solution.

Thanks a bunch TIG, I forgot you could get the arcs edges! Still organizing all this information

@tig said: You are only ever giving us half the story... Sorry about that! I clearly had some difficulty thinking outside the box. The empty definition did not work in this case, so I added a dummy line definition entity and erased it. #----Do dummy line entities = def_stair.entities # def line = entities.add_line (@p8, @p7) entities.erase_entities line all is well now, thanks! [image: ApAv_stair1.png]