@ktkoh said: The problem was that some entries were interpreted as strings. UI.inputbox returns values in the same class as you feed the defaults. So if you feed it Lengths it returns lengths.

Hi Keith, Don't use GetString just because Google's example scripts do. Do you know the purpose of GetString, how it works, or in which file it is defined? (it's in /Tools/langhandler.rb)

<span class="syntaxdefault"><br /></span><span class="syntaxcomment">#&nbsp;pt&nbsp;=&nbsp;point&nbsp;in&nbsp;group1<br /></span><span class="syntaxdefault">pt</span><span class="syntaxkeyword">.</span><span class="syntaxdefault">transform</span><span class="syntaxkeyword">!(&nbsp;</span><span class="syntaxdefault">group1</span><span class="syntaxkeyword">.</span><span class="syntaxdefault">transformation</span><span class="syntaxkeyword">.</span><span class="syntaxdefault">inverse&nbsp;</span><span class="syntaxkeyword">)<br /></span><span class="syntaxdefault">pt</span><span class="syntaxkeyword">.</span><span class="syntaxdefault">transform</span><span class="syntaxkeyword">!(&nbsp;</span><span class="syntaxdefault">group2</span><span class="syntaxkeyword">.</span><span class="syntaxdefault">transformation&nbsp;</span><span class="syntaxkeyword">)<br />&nbsp;</span><span class="syntaxdefault"></span>

Yes. That's what I remembered. That's why it doesn't work for my needs. Still it is good for what it is intended for.

obviously no help to you but just in case a mac user wants to do this, sync these files: via - Macintosh HD > Library > Application Support > Google Sketchup 8 > SketchUp %(#BF0000)[plugins Components Tools Materials Styles] via User > Library > Application Support > Google Sketchup 8 > SketchUp %(#FF0000)[Shortcuts.plist Templates] via User > Library > Preferences com.google.sketchuppro8.plist [most of these are obvious as to what they will do and all of them aren't necessary.. the last one (com.google.etc) will sync toolbar positions, startup template, units, etc.]

Thanks for the router drawing that was just what I was looking for. I will post the model again when more details are complete. Keith

Thank you for sharing!

As with any thing that would appear in the Context menu, in order to see it in the Shortcuts list, the state of the drawing must be such that it would show in the context menu. Select a component (single click) and then open Window>Preferences>Shortcuts. in the Filter line, type Flip and you should see the three Flip options. Set the shortcuts as desired. Click OK. After you've set those, either open the component for editing and select the geometry or select two components and repeat the process. I use F2, F3 and F4 for Flip along Component's Red, Green and Blue and Shit+F2, Shift+F3 and Shift+F4 for Flip along Red Direction, etc.

Thanks that was a lot clearer than the docs. Keith

@jim said: By the way, what is the difference between a page .name and a page .label? Seem to be the same, except label doesn't have a setter... The examples for the getters are pretty much the same.

Thanks that fixed the problem. I will look at the graphics drivers also Keith

I added .name (Sketchup.active_model.selection[0].layer.name) and got exactly what I needed. Thanks Keith

And if you want to create components, then you use model.definitions.add "newCompName" http://code.google.com/apis/sketchup/docs/ourdoc/definitionlist.html#add And then place an instance of the definition. http://code.google.com/apis/sketchup/docs/ourdoc/entities.html#add_instance Instead of making a groups and then converting the group.

TIG thanks that worked like I needed it to. Next time I'll remember to add the code brackets. I am in the process of adding features to my makepart ruby and as someone wrote the monkey see monkey do coding only goes so far. Keith

Keith, I'm glad that took care of it.

I will try to explain with more detail. The board to have a mortise/tenon must first be a component. Rotate to a view where you can see the surface that will have the m/t. After selecting the tool the help text states select the component. Do this by mousing over the component and left mouse click. Next help text states select first edge parallel to mortise length. A typical m/t is longer than it is wide ( 2" x 1/4") so click one edge parallel to the longer m/t dim. Next help text states select second edge parallel to first edge. Click on that edge. Fill in the form with your dim. Edge1 to m/t length is the offset for the m/t from the first edge you selected. For a 1/4" mortise on a 3/4" board this would be .250 to center the mortise. The other edge to end for a 2" mortise on a 3" wide board would be .50 to center the mortise. I hope this helps Keith

hi tig, ok, let's play with some formulas thanx stan

Ooops! I think I misunderstood your question. On the form the To distance is the distance from the first edge selected "to" the dado. The To Edge is either To, Center, or Over. To is the first or leading or nearest edge, Center means the dimension is to the center, and Over mean the farthest edge. Almost always, one would use the To edge. Selecting the To edge and a To Distance of 0 creates a rabbit. Sorry if this is confusing. It all makes sense to me, but probably nobody else.

As I understand SU when I leave layer0 as the active layer then all of the components details or drawing information remains on layer0 and moving it to a new layer via the "I" information form only affects the visibility of the component. So that is what I want to do the same as if I selected the component pressed "I" and changed the layer to new layer I just created. I hesitated to use the term move the component to the new layer as I understand that is not really what happens. My layer management plan for woodworking projects is such that each part is made a component and has a Assembly layer (A01TableTop) and a part layer for the dimensioned drawing (P01TableTop). I also have an Assembly Scene that makes all the parts in the assembled position visible. My box.rb now creates these layers as hidden so they don't show up in scenes where they are not wanted. In a perfect world for me box.rb would also: 1.Place the first instance of the component on the new named assy layer. 2.Place a copy or second instance of the component on the new named part layer. 3.Add the assembly layer to the Assembly Scene. Thanks Keith