Thank You So much,Tig. It works ! This is the idea to revise a model from architect by storing data at the first time. And later use to recheck data for tagging panels , and take the panel out in order that the facade engineer can do the life size panels to do mapping back on sub-dividing panels. The method I do : The subdividing faces are in the "Layer0". The patterns are in the Layer-"Patterns". So , they are not mix together in the same layer. For the shortage time to "delete coplanar edges or patterns" , I have to select edges by degrees and use your code to delete edges because the group edge and original edges are overlap that I have to delete original edges.So , it doesn't affect to bring tagging panels out , and I can recheck the patterned data to do retag panels. For the store patterned data , maybe it comprise of 3 functions : 1.Make edge group 2.Select Coplanar edges by degrees 3.Delete Coplanar edges selection

@curator said: How can I add, sets say, an option like "change radius" or "change position". How do I add such an option only to "sphere", and not to "cube" or whatever. IF you use a group: UI.add_context_menu_handler {|menu| sel = Sketchup.active_model.selection if (not sel.empty?) && sel.single_object? && sel.first.is_a?(Sketchup;;Group) && sel.first.entities.parent.name == "Curator_Sphere" menu.add_item("Change Radius") { # do code here, or call a method like; Curator;;SphereWorx;;set_radius(sel.first) } end } IF you use a component instead: UI.add_context_menu_handler {|menu| sel = Sketchup.active_model.selection if (not sel.empty?) && sel.single_object? && sel.first.is_a?(Sketchup;;ComponentInstance) && sel.first.definition.name == "Curator_Sphere" menu.add_item("Change Radius") { # do code here, or call a method like; Curator;;SphereWorx;;set_radius(sel.first) } end }

At best it will find a match immediately 1/2000, at worst at go 2000/2000, on average at go 1000/2000. You can but test it and see... If you are adding all cube-instances in the same SketchUp session then why not make a @points array to push [ <<] all of the points you will use during the placements - these need to be as arrays so they are 'comparable' [use point.to_a] - points are comparable as == but include? is faster [most probably] with array comparisons ? Then... instead of finding all instances and comparing each 'instance.origin' to 'point' use: @points.include?(point.to_a) If the tested point is in the current list then it's taken and you skip the operation... Of course this doesn't work when instances have been erased or across SketchUp sessions

That will be released later as we get closer to releasing SketchUp 2014. We cannot release all the details publicly yet. We do have a great amount of recordings from the event.

Ah, Good point sl. I used a similar test for a line-plane intersection test.

Dan Rathbun I can't thank you enough you sir are brilliant!

In this example I increased the width of the stringer which results in a small triangle that you can see. Width is 304 mm. Where the sketchup error occurs the stringer width was 300 mm and the small triangle would not be visible at this zoom. What I have done for now, which works in these type of situations, is simply use a rescue block. I would normally consider this bad form as it can hide errors. This code only works on the last section when the stair has a heel and when we should have a triangle. The sketchup error was misleading and cost me a bit of time trying to track this down. begin # try to add the face ent.add_face( pts ) rescue puts( pts ) if ( debug_level > 0 ) end Any thoughts on this? [image: EYAC_collinearissue.JPG]

@massimo said: Moved to developers forum. Hi Stan, would you mind to post such threads in developers section of the forum? Usually the newbie section is about SU's usage. Thanks. hi massimo, sorry, of course, didn't think about that , i'll be carefull in the future! stan

The unexpected reversion of smoothed edges to solid is a known bug. Never save when in a edit session. Even an auto-save can trigger this, so never stay inside an edit session for longer than you need to...

You're not going to believe me, but the puts wasn't working in the Ruby console for the past 2 days, but it just started working right now. Ghost in the machine I guess. I'm still getting a crash when I run the motion_sample.rb script I mentioned above. I think it might have to do with not being able to access the gems, although there is no error message. I'm investigating it and will get back with any questions. Thanks again!

You should study the drawline.rb in the "Examples" sub-dir.

The native 'select' tool will often return its array in the order of picking, BUT this is not guaranteed, and of course if you pick a curve, then all of its edges are added in the curves edges' order... You can make a Tool class... where the selection is initially cleared and the user is prompted to select things - these can be added to the model.selection, and also in that case each selected object can be pushed into your own array, so you can be sure of the order of that array's order of picking... What is it exactly your seek to achieve ?

hi tig, that's it . my logic was ok, your tip for the conversion of string to float was the point. basicly it works like this: i have menues for parameters then the geometry is created before the end of the ruby i save all parameters to a text file (by the way still looking for the syntax to save more of them line by line) then the user can recall the ruby and select -my last parameters -defaults and so on and so on again another step!!!! regards stan ( i'll report , when i get further)

hi tig, you are the greatest, as always. it works. it's funny, that "my" wrong syntax works at the beginning of the ruby...god knows....will correct all of them. again a step nearer to my first ruby (for everyone then, of course) regards and thax stan

Hi, With the introduction of 'PluginStore' and 'Extension Warehouse' it has become more accessible for developers to share plugins and maybe in the near future these platforms will allow authors to sell them as well. (fingers crossed) As of right now donations are a welcome addition to 'PluginStore' and even though there are people who have generously donated, this kind of appreciation is considered a rare event. Most of them will thank you by leaving a nice comment and this can be very rewarding as well. Selling plugins will hopefully inspire developer to increase the production value of their plugins so they can have an edge vs competitors. Not only the code should improve but also the interface, graphics, documentation, ect... On the other hand I am afraid to see the dark side of competition which I am sure you guys can think of a few. Cheers!

There is no inbuilt method... but this will do it [flattened to Z-plane] def flat_angle(vector) vec=Geom;;Vector3d.new(vector.x, vector.y, 0) if vec.y < 0 return (2*Math;;PI)-(vec.angle_between(X_AXIS)) elsif vec.y > 0 return vec.angle_between(X_AXIS) elsif vec.y == 0 if vec.samedirection?(X_AXIS) return 0 else return Math;;PI end end end it's easy to make methods for X & Y planes - just adjust vec= to suit those other planes and adjust the tests from vec.y & _AXIS etc...

@abakobo said: what's behind the :: symbol in Geom ? It is called the scope operator. :: with nothing to the left of it means the top level scope (aka TOPLEVEL_BINDING,) which is "a particular instance of Object called 'main'". But it's use that way is optional. Ruby always checks the current scope first, then the top level scope if it needs to. But this is also why you should always be executing YOUR code inside a toplevel module, with some unique name that you invent. like module Abakobo So Geom::Point3d is referring to the Point3d class, within the Geom module scope. @abakobo said: and when do we use :: and/or . to call a method It's style, but many people only use the . for ALL methods. Some people use :: for calling module functions and class methods (which the new constructor is,) and then use . to call only instance methods. (Some of the older examples, from the days when SketchUp was owned by Google or @Last Software, use this latter convention. I guess they wanted to emphasize the calling of class methods or module functions.)

Can you send me the RB and RBS file you are working with? I'd like to hook this up to our own debugger.

It's a pseudo-code. The actual code implies that observer object is a class instance variable: class Scene attr_accessor(;observer) def initialize @observer = MyEntitiesObserver.new end def observe Sketchup;;active_model.definitions.each do |definition| definition.entities.add_observer @observer end end def unobservre Sketchup;;active_model.definitions.each do |definition| definition.entities.remove_observer @observer end end end