Shouldn't you swap the results of the key-up and key-down events ? You hold the key down it spins, release it and it stops ? Take the self.spin_it out of the activate method, it's run when there's a key-DOWN event anyway. When there's a key-UP event it sets @stop_spin=true, so the 'until test' should expand to be until Time.now - @start_time > 10 **or** @stop_spin and you should remove the matching break from inside the loop too as the until breaks it anyway...

You can't prevent an object from being erased. You might be able to recreate it, if you manage to get any info on the erased entity (which is usually garbage by the time the oberser reports it), but you will very likely end up interfering with some other operation. Safer and easier might be to create a custom Erase Guides function that will omit your protected guides. It would be a useful tool, as I've also experience your frustration many time myself. You could use attributes on each entity, or you can use attributes on a layer. Both options would be useful.

No reason, but I went ahead and changed the posts to this account to avoid further confusion.

Two Monitors. One has the drawing window, the other has all the toolbars and windows.

@chris88 said: the problem is solved I'm curious to what it was...

Sounds to me like you made a component instead of a group...

Great! Thank you, i like this forum more and more. Merry Christmas and happy holidays to all!

And remember that a group or component can be skewed, affecting the area calculation as well.

Hi Keith, Thanks for the input. As stated some features aren't working yet... as you found out right now you can't mix and match doors and drawers. Which in turn is why you're not asked anything about drawer size... when adding drawers to base cabinets they automatically divided equally in the size of the cabinet entered. Ecepth when selecting 3 drawers then the top is smaller then the bottom 2... I'll be adding the option to have 3 equally sized drawers. Like I said this was for personal use with the way I build cabinets so I understand that some deatures seem limited... but I figured it was hard enough to get what I wanted without adding options I would never use. But I'm kinda getting the hang of this and add different features as I go along and have the time. So far it's proven very useful in getting exact measurements for things like stile and rails which I use to have to calculate individually for different cabinets, now it's all done automatically which to me is a huge time saver. As per Dan's suggestions I'm working 'standardizing' the pluggin and when I'm done with that I'll start a new thread dedicated to the plugin with updated. I guess till then this thread can be used for suggestions. Frank @ktkoh said: Tested your cabinet plug-in and was impressed. However I was trying to design a base cabinet with 2 drawers at the top and then doors on the lower part of the cabinet. What I got was a 30" tall base cabinet with 2 doors and then 2 drawers on top of the base cabinet with a total height of about 50". Also when I specified drawers I was not asked anything about size. I'm sure there are too many options to please all cabinet designs but I would think this would be able to get a kitchen design started and the individual could add/change some details with less work than starting from scratch. Keith

First of all, I'm also russian, you can write the post in russian and in english (if want to)and i'll reply in two languages. So, what you wanted was to get hotkeys input? The actual plugin hookproc can't get hotkeys (key-combinations) input, though there should be a way to get it. I'll do some research on it... and then write a plugin for that.

You could try with the transparency flags of .start_operation .

hermann, The problem is that if you use edges or curves to add a face, they must form a closed figure which yours doesn't. What you need to do is extract and use the vertices of the two arcs to define the face. So after the first arc, add verts=arccurve.vertices. After the second arc, add verts+=arccurve.vertices. The add_face statement would then be face=entities.add_face verts. model = Sketchup.active_model entities = model.entities group = entities.add_group entities = group.entities # Halbkreis nach rechts / half curve to right center = Geom;;Point3d.new 150.mm,0,0 normal = Geom;;Vector3d.new 0,0,1 xaxis = Geom;;Vector3d.new 1,0,0 start_a = Math;;PI/-2 end_a = Math;;PI/2 edgearray = entities.add_arc center, xaxis, normal, 50.mm, start_a, end_a edge = edgearray[0] arccurve = edge.curve verts = arccurve.vertices # Halbkreis nach links / half curve to left center = Geom;;Point3d.new 50.mm,0,0 normal = Geom;;Vector3d.new 0,0,1 xaxis = Geom;;Vector3d.new 0,1,0 start_a = 0.0 end_a = Math;;PI edgearray = entities.add_arc center, xaxis, normal, 50.mm, start_a, end_a edge = edgearray[0] arccurve = edge.curve verts += arccurve.vertices face = entities.add_face verts status = face.pushpull 20.mm

[image: suscreen] That helps me inject "Help" codes into each script i do not remember how it is operated. just changed a few codes on youtube embed. m.add_item('HELP..clean3..') { link_value='<object style="height; 390px; width; 640px"><param name="movie" value="http://www.youtube.com/v/seJYub0LCmQ?version=3&feature=player_profilepage"><param name="allowFullScreen" value="true"><param name="allowScriptAccess" value="always"><embed src="http://www.youtube.com/v/seJYub0LCmQ?version=3&feature=player_profilepage" type="application/x-shockwave-flash" allowfullscreen="true" allowScriptAccess="always" width="640" height="360"></object> ' @dlg = UI;;WebDialog.new "CleanUp³ YouTube Help " html_string = "<html><body leftmargin=1 topmargin=1 bottommargin=0 marginwidth=0 marginheight=0>" + link_value + " </body></html>" @dlg.set_html html_string @dlg.set_size 680, 410 @dlg.show p html_string }

Hmm thanks TIG, i'm going to look into that. Quintus

If you are drawing these double lines on a 'surface' then picked-point at point1 can be used to return the best face below it - get the axis=face.normal... If it's not on any face or you want it flat then axis=Z_AXIS Then next picked_point point2 needs to be on that face, so get it's initial value and then use point2=point2.project_to_plane(face.plane) or if it's to be 'flat' use point2.z=point1.z instead so it's level with point1... This gives you the first edge edge12=entities.add_line(point1,point2) To make it's offset 'clone'... Assuming ' width' is the offset required. point3=point1.offset(edge12.line[1],width) rotate it into place... tr=Geom::Transformation.rotation(point1,axis,90.degrees) point3.transform!(tr) get the other end point point4=point3.offset(edge12.line[1],edge12.length) and then draw the offset edge edge34=entities.add_line(point3,point4)

@jim said: My understanding is that at least some of the SketchupExtension instance methods are meant to be called by SketchUp rather than by plugins. Yep. If interested, just read comments in the new extensions.rb file in the Tools dir.

@dan rathbun said: Not in the global Objectspace, no... ... all your code should be inside your unique toplevel module, and all your classes should be inside that as well. Okay, that's what I thought. It was just the wrong use of variables, and people who were learning ruby from sketchy physcics scripts did the same thing, so now I know, Thanks

Hello, Thank you very much, I am going to look at that.

I used this code in my joint tools and found it very useful as the user could enter equation if they do not know the actual value. However I could not make it work if the user entered the " for inches as sketch-up does. Keith