@daiku said: @jeff hammond said: . (is this a ruby question or an ill_located thead?) Am I not in the developers forum? yes, you are. every thread isn't always started in the right forum though and your question could be answered in a sketchup way or a ruby way.. the first answer to your question was how to figure it out in sketchup. hence my question. [+, many members (myself included) browse the forums via the 'new posts' or 'active topics' lists so sub-forums aren't always so obvious since we're basically seeing all forums in one view.. some confusion is bound to happen here&there.. it's ok]

Worked Perfectly. Thanks, Tig!

Cool use of Morse

I think that the default-layer is now called 'Layer0' in all locales... BUT there was a time that it was named differently for each locale-version. So entity.layer=nil WAS [still is] the safe and correct way to default the object's layer, without recourse to using a 'name' at all... Similarly entity.material=nil and face.back_material=nil will also default those, without recourse to using a 'name' at all...

@tig said: Moving one vertex and then perhaps another will often have a quite different results, compared to moving them all in one fell swoop with the entities. transformation methods that do all of the changes together... Plus - it's much much faster to perform one big entity transformation instead of many.

For your "point and plane test" it's easy enough to make your own tool's method without messing on with any base-classes... def point_test(point, plane, cond=false) ### 'point' is the point to test, ### 'plane' is the plane to test and ### 'cond' allows you to return true/false IF point is ON the plane. ### NOW add your code here that see if the 'point' is on, in front or behind the 'plane' ### returns 'behind' as 'true' or 'false', with a tweak for the 'cond' setting if behind return false else return true end#if end#def Then in other code within your toolset use self.point_test(point, plane, true) where 'point' is to be tested for its relationship with 'plane', and here the third argument 'true' says to take 'point' as being 'in front' even if it's ON the plane too... [you would use no third argument or 'false' if point ON plane is to be 'invalid']

That's about it! If the plane is from a face the face.normal is easily found. You could also extract the plane's vector from it's 'array' ? Project the original_point onto the plane, then offset! that cloned_point along the plane's 'normal' vector by the distance between the original_point and its projected cloned_point... and then if cloned_point == original_point the original_point is in front of the plane, otherwise it's behind the plane; you should also check separately for the original_point being exactly on the plane... and decide whether that counts or not.

The same here with the model under "Series #2" (the curved hotel building) here: http://forums.sketchucation.com/viewtopic.php?p=264568#p264568 It was really a time saver and made it extremely easy to do it with the new feature.

Hi, I noticed that the plugin paints segments - not like SketchUP's paint utility. Can be made to behave the same? [image: 2y4Q_2010-12-09_101234.png] [image: wzra_2010-12-09_101323.png]

take a look at EasyGroups

@tboy said: Any updated info for this topic? YES. (5 years after this thread ...) In the SketchUp 2015 release, a new key was added to the RenderingOptions hash: The key is: "DrawBackEdges" See API documentation: http://ruby.sketchup.com/Sketchup/RenderingOptions.html

You can also take an object oriented the way you want your plan, and create a new axis using that object. For your new axis blue is still on the Z axis for your model, set the green axis to go in the direction that you want to be at the top of your screen in plan view. You can save this as a scene and always jump back to it.

Thanks Tig. My tools are specific to a very specialized group of users (timber framers), so they'll know what should be selected. I think having the tool grayed out on the menu is all I need to do. CB.

@thomthom said: I think that as a component/group is opened for editing, all co-ordinates are made global. That explains much. @thomthom said: Su7.0 introduced a method to help on this matter: http://code.google.com/apis/sketchup/docs/ourdoc/model.html#edit_transform And I'll have to transform them all back myself, I guess. Thanks, Thomas.

Sorry about bumping my own thread, but I'd really like to solve this one. The built-in rectangle tool does exactly what I want. You can see it by watching the VCB. Even though you are at a diagonal distance from the the first point, it snaps to even numbers in the cartesian directions. I started with the line tool sample, but I modifed the VCB code to display the x and y offset values rather than the striaght-line length. But they are always some odd value with a ~. CB.

@daiku said: Clearly I was overthinking it! Thanks, Thomas. Something none of us have ever been guilty of before Chris

@daiku said: I guess Martin's way is fine. It won't create a second face, will it? Yes, I'm creating it on an exisiting face. Looping through the geometry was straightforward - it's not that large a component. In that case you should only need to check the faces collection of one of the returned edges.

Having a similar problem here. It started while trying to draw a triangle onto a flat surface to copy/flip/paste as the basis of a dormer on a house. After laying out the coordinates with Tape Tool, I drew out the first right triangle. The guides shifted as though it was slightly under the surface, and fazed in and out as I navigated. When I attempted to copy, the entire surface was highlighted. This is an enclosed geometry issue. I sent all layers to the default and attempted again to confirm. Same problem. I then noticed that the guide was shifting not just in and out of view, but to the left and right of the line drawn onto the guide. The issue seems to be progressive. I just upgraded from A 8800GTS 512m to a 650ti 2g about 2 weeks ago and have completed about 15 projects maxing at about 6000kb. This only begun last week, and is occuring in the begining of the project at about 2000kb.

Yeah, I tried it and I also get the errors. I should have tried sooner. There are other tools that send errors to the ruby console too. Oops! So I would say it is woorking as expected. Chris

Interesting, I'm not seeing that. Perhaps you have a ruby installed that is conflicting. You might need to test which ruby it is.