@dacastror said: @thomthom said: In SU2014, yes. What would be the best way to write this for Sketchup 8 or 2013? (google translator) In SU8 and SU2013 and older that method is bugged. No known workaround I'm afraid.

Yeah, that should work. Thank you.

Hi Guys, Thanks for the replies. I wanted to do the way I described, cause that way the user could use any tool available to him. But, as it turns out, this seems undoable. I ended up creating my own line tool that would do what I wanted.

Thanks Dan, this can give me a hint, I'm testing with the definition given there, but in my testing model (instances.skp) gives me a wrong number of instances, sometimes less or sometimes more, I do not know if I'm misapplying the definition count_instances () # you must have a selected instance def count_instances() num = 0 if @editpath.size == 1 i = @editpath.last else revpath = @editpath.reverse i = revpath.shift end if i.is_a?(Sketchup;;ComponentInstance) num = i.definition.instances.size elsif i.is_a?(Sketchup;;Group) num = i.entities.parent.instances.size end if @editpath.size > 1 revpath.each {|i| if i.is_a?(Sketchup;;ComponentInstance) num = num * i.definition.instances.size elsif i.is_a?(Sketchup;;Group) num = num * i.entities.parent.instances.size end } end return num end mod = Sketchup.active_model sel = mod.selection ruta = mod.active_path (ruta) ? (ruta[ruta.size] = sel[0]) ; (ruta = []; ruta[0] = sel[0]) @editpath = ruta count_instances()

In my case, LibFredo6 is registered as a true extension. If you disable it from the Extension Dialog box, then all my scripts relying on LibFredo6 will be disabled. I do agree that SU should provide some built-in support for scripts relying on a common library as this becomes more frequent: managed the requirement of the Lib possibly check its version for compatibility Fredo PS: I wonder why there is a field requirement when you upload a plugin, but it is not displayed in the PS tool browser window.

Updated (2014-03-16) to copy properties of old instance to the new one.

@dacastror said: ... Dan, but I think you need to add the following properties; material, attribute_dictionaries, layer, description, entity_name, name, receives_shadows, casts_shadows I wonder if there are more properties that can be inherited by the new instance (google translator) Yes you are correct. Just before the old instance is deleted, it's properties need to be copied over to the new instance.

hi dan, this is a special IGS format what needed by the game

Thankyou - this will be a good read! I currently test on SU 7, SU 8, SU 2013 and SU 2014. The work around is easy enough.

Either that or we get the old blog up and running and link more extensive info from the docs to these longer pieces of info. Or some wiki thing. We still working on getting a better system up. Got a long list of topics to clarify.

As I recall from the last build cycle (2013,) the Sketchup::Page and Sketchup::Pages classes had issues filed on them regarding updates not working correctly. (As well as a bunch of feature addtions, by myself.)

2014 Sticky palettes are back !!! Now how about bringing back thumbnail icon of SkUp files in Finder. Was there up to v8. So practical. Anyway very happy with v2014. Full congrats to the SU team !

Thanks, that might come in handy!

I checked your extensions to invoker c#from ruby at https://github.com/icehuli/suWpfExt. I used to use win32ole to invoke my c# extensions. But since SU2014 and ruby 2.0I could not get anything up and running yet, either icehuli extension or my win32ole calls...

Al.. I PM'd you an idea.

@tig said: Never include a space between the method and the opening parenthesis that is enclosing its argument[s]... I was going to tattoo that statement on my arm, but my Wife wont let me. Regardless, I have often wondered what goes through the mind of those that write computer languages. What fantasy world do they live in? It would not be very easy to read a sentence without spaces between words, would it?

By default a texture's 'grain' always follows that axis, so your make-the-parts-rotated_and_then-rotate-them-into-place method is a winner. I think in your case it's the best approach... However, FYI you could also change the orientation of a texture for certain faces 'in code' - just like you might when using the manual 'Texture' tool - from the context-menu when a textured face is selected. I [and others] have written several UV / Texture tools - which move, scale and rotate textures - look at their code for ways to transform some UVs and then apply them to a face.material.texture... http://sketchucation.com/pluginstore?pln=TextureRandomizer http://sketchucation.com/pluginstore?pln=TIG-TextureTools

Who cares? The second one is not the format given in the API dictionary. Use the first one.

@jim said: Correct, Ruby does not process the lines between. They are typically used for block comments. And if used, the equal sign must be the first character in the line (no whitespace.) Thank you for the answer. that helps me understand a bit more of ruby scripting

Thanks.