There appears to be a software defect in the SketchUp API. Loading the textures into TextureWriter and then attempting to access their filenames using TextureWriter.filename(index) returns only empty strings. However, if you call TextureWriter.write_all beforehand: # Display texture names def display_tex_names $tw = Sketchup.create_texture_writer load_textures(Sketchup.active_model.entities) $tw.write_all("D;", false) tex_index = 1 while (tex_index <= $tw.count) UI.messagebox($tw.filename(tex_index)) tex_index += 1 end Sketchup.active_model.commit_operation end then the filenames are returned properly. Confusing matters further, the TextureWriterindices are one-based rather than the expected zero-based array.

I have tried but seems I can't get it to work or understand correctly. Is there a sample code that can better illustrate this. Thanks!

Assuming f is the reference to the intersecting face object: a = f.area() See the API Face class.

Hi, May I know after determining if the 2 groups/ components/ faces are intersected. How do I get the area of the intersection?

@unknownuser said: Add:: On Material - I am actually happy that the default material returns nil because it may pass as a mask feature But this line will cause an error: if flags == 1 && @@sel != nil && @@texture_addon == true && selected_face_mat.texture != nil If selected_face_mat is nil then you cannot call .texture on it.

Then it sounds like moving to an Ruby C Extension is what might give real performance improvements.

@thomthom said: Gerrit, you mean like my Vertex Tools? Where it offers a set of Move, Rotate and Scale tools for vertex editing? ....... Thank you Thomas. No, I meant the most basic thing where, once a plugin is loaded at startup of SketchUp, the plugin is right available in the menu where you let it appear. And at the same time the plugin can (from thereof) also be reached if you assign a shortcut key to it. I wasn't sure whether "placing in the list" was done automaticaly or if you need to have some extra code in the plugin for the list. Example: I place plugin "AAA" in the folder. Looking at the code I see that "AAA" will show up in menu say "Draw". Looking at the shortcut list I can see that I can assign its use to a key. In my case I don't want to use my plugin through any menu but (say lazy as I am) by hitting a key. As it seems SU handles most of that for me. As long as I let it appear in a menu and than find it in the list of shortcuts for assigning it. Thank you Aerilius, for confirming TIG's answer. The idea I have (and have had for a long time) is simple and takes all you writers about two minutes to write. I just want to put this together myself, as simple as the idea is. Otherwise I'll never learn.

@mattc said: def initialize() > sel=Sketchup.active_model.selection > SPP;;test_start > SPP;;check_selection(sel) > SPP;;test_end > end (4) The above is not correct. The initialize() method is only used in a class definition, where you wish to let the user create MANY instances of the object. Users will not need to create many copies of your plugin. Most plugins are code that needs only one copy, .. so it should be a module (inside your author module.) But a plugin module can have (and often does,) use custom class definitions and instances inside it's module. Later on, you will likely be creating a custom Tool class inside your plugin module.

@aerilius said: I've done similar experiments and found evidence that Threads do (partially) work. And ... in PC SketchUp prior to v8, it distro'd with Ruby v1.8.0 in which the Thread class was very unstable. But threads have gotten more stable in Ruby versions above v1.8.6, even more so in the v1.8.7 branch. Keep in mind that all the Mac Sketchup editions still disto with Ruby v1.8.5 (initial release.) Usually .. coders wish to use threads in order to prevent SketchUp from blocking. As ThomThom said.. threads in the Ruby 1.8.x trunk are green threads (still within SketchUp's process.) Read the description of Green Threads at wikipedia. DITTO what TIG said.

@honkinberry said: The javascript:void(0) is the recommended practice, indicating that the onclick handler is to take precedence. I disagreed 3 years ago when we discussed this issue, and still do. Read my detailed explanation in this old thread: Webdialogs and Javascript void Any more discussion on this offtopic, can be done in that thread, if you wish.

UPDATED code in 1st post to v2.0.1, in refresh() method's next statement to avoid a vicious loop. (We use Hash#has_key?(key) rather than Hash#[key]!=nil, because our v2.0.0 update makes the [] method call the refresh method, so we must be very careful from within the refresh method that any [] method call does not cause a unwanted or unneeded, call to refresh.)

Personally I have just used a Ruby %x call using the fciv.exe command line checksum utility that I believe came with the Windows Support Tools. fciv stands for File Checksum Integrity Verifier: Microsoft Download: File Checksum Integrity Verifier

@burkhard said: Found a workaround. It needs to be refresh, ... So, if a Toolbar is not loaded, it works after refresh the hash. The Toolbar WAS loaded, but UI::Toolbar references are NOT automatically added into the custom User::ToolbarSet hash. SO.. I created the UI::Toolbar.refresh() method to find any new toolbars (created after the hash was populated,) and add them. I WILL NOT modify the API's UI::Toolbar class constructor method, in a public script, because I feel it is a violation of the API Terms of Use. BUT perhaps we can modify the User::ToolbarSet hash's [] method's error Proc, so that it refreshes the hash automatically. See: http://sketchucation.com/forums/viewtopic.php?f=180&t=51432&p=466742#p466742

TT added commenting to the original code block to try and explain things better, I can't get the formatting to hold... but this is better. john

@mptak said: I think this will inspire me to finally make the leap fully into github! Excellent! I'd really like to see the SketchUp community making more use of tools such as GitHub and BitBucket etc.

<span class="syntaxdefault"><br />filter </span><span class="syntaxkeyword">=</span><span class="syntaxdefault"> File</span><span class="syntaxkeyword">.</span><span class="syntaxdefault">dirname</span><span class="syntaxkeyword">(</span><span class="syntaxdefault">File</span><span class="syntaxkeyword">.</span><span class="syntaxdefault">dirname</span><span class="syntaxkeyword">(</span><span class="syntaxdefault">__FILE__</span><span class="syntaxkeyword">),</span><span class="syntaxdefault"> </span><span class="syntaxstring">'*.rbs'</span><span class="syntaxkeyword">)<br /></span><span class="syntaxdefault">for filename in Dir</span><span class="syntaxkeyword">.</span><span class="syntaxdefault">glob</span><span class="syntaxkeyword">(</span><span class="syntaxdefault">filter</span><span class="syntaxkeyword">)<br /></span><span class="syntaxdefault">  eval</span><span class="syntaxkeyword">(</span><span class="syntaxstring">"Sketchup;;require('#{filename }', TOPLEVEL_BINDING, '#{filename}', 1 )"</span><span class="syntaxkeyword">)<br /></span><span class="syntaxdefault">end<br /></span> ?

I'll post some cut tests shortly, but here is the lovely curve: [image: RnQR_bezier160.JPG]

this: normal_vector = normal_vector + face.normal will not work as expected, if you set normal_vector to reference the integer object 0, because the integer +() method will get called, and it is not likely that it would know how to handle an argument that references a Geom::Vector3d object. Smarter to create either a unit vector object to start with, or a zero length vector: normal_vector = Geom::Vector3d.new(0,0,0) THEN, when you call the +() method using: normal_vector = normal_vector + face.normal the special vector addition API method will get called. In other words your statement is evaluated as if it were written: normal_vector.=( normal_vector.+( face.normal ) ) This is one of the important things about Ruby... = and + (etc,) are not really operators, they are instance method names.

This seems to work with or without using intersect_with model = Sketchup.active_model entities = model.entities entities.clear! #Create a group to collect all entities for base cube basegroup=entities.add_group basegroupentities=basegroup.entities base_trans=basegroup.transformation p1 = Geom;;Point3d.new(0, 0, 0) p2 = Geom;;Point3d.new(9, 0, 0) p3 = Geom;;Point3d.new(9, 4, 0) p4 = Geom;;Point3d.new(0, 4, 0) points = [p1,p2,p3,p4] base = basegroupentities.add_face points base.reverse! if base.normal.z < 0 base.pushpull 1 cutgroup = entities.add_group() cut_trans = cutgroup.transformation cutgroup.entities.add_3d_text('Bob', TextAlignCenter, "Arial", true, false, 3.0, 0.0, 0.0, true, 1) transform = Geom;;Transformation.new(Geom;;Point3d.new(0.5,0.5,0)) cutgroup.transform! transform #intersections = cutgroup.entities.intersect_with true, cut_trans, basegroup.entities, base_trans , true, basegroup basegroup.explode dmp=cutgroup.explode;#erase the top and bottom of the letters dmp.each{|f| f.erase! if f.is_a?(Sketchup;;Face) && f.normal.z.abs>0.5} #add faces to 'holes' in the letters dmp.each{|e| e.find_faces if e.is_a?(Sketchup;;Edge) && e.faces.length==1} model.active_view.zoom_extents

Surely an instance variable will work just as well? Avoiding the risk to collision of global variables - especially with a common variable name such as args.