Just looking for a shortcut way to get vertex normals. I know it can be done in Ruby, but was hoping SketchUp did it faster when using a PolygonMesh.

Thanks, that's very helpful (and I was also wondering why such observers don't exist, good feature request). I'll have to consider this for my webdialog callbacks.

sweet! exactly what i was looking for. thank you sir

An easier way is to make menu macros for the context menus (the right-click popup and the Edit menu's selection submenu.) FYI: I posted a boilerplate sample

You already know how to add objects to an '.entities' collection [i.e. for model/active_/definition/group]. Make a new definition, then use defn.entities.add_instances of the other three [already made] components as you wish... OR make the containing definition, then make gp=defn.entities.add_group() and add geometry etc to gp.entities, make the group into a component and then adjust its definition name etc as needed - repeat three times for the contained instances...

Thank you very much TIG for your work. Your ShadowProjector is great and I'll try to do some reverse engineering on it

ah.. ok.. i see @driven said: the easiest way to load individual plugins is to click add, and under a new Plugins menu there's only Plugin Loader, submenu load single plugin. as you add them your menus grow and the work as normal. yeah, i want to set skindigo up to do this (it messes with the new windows so i can't close them super easily).. can you also turn an individual plugin OFF with this? [ie- load skindigo when i want but easily prevent it from loading on my next launch?] that said, i do have a request in to whaat to make skindigo an extension or try to fix the mac error.. this would work well until that time.. i'm currently renaming skindigo in the plugins folder to keep it from loading when i don't want it.. kind of a hassle..

Did you read ThomThom's: WebDialogs - The Lost Manual — R1 2009NOV09 specifically the section on "Async vs sync Communication"

do you read your PM's or check for answers? john

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.