I started a new encoding bug topic incase it's unrelated... http://sketchucation.com/forums/viewtopic.php?f=180%26amp;t=57074#p518534 can you all have a look? john

Thanks to Driven and Dan. I will use new notation instead use force_encoding. I think now it should works... #UUID in RUBY 2.0 WINDOWS ` cmd="wmic csproduct get uuid" filename = File.join(ENV["TMP"],"backquote.out") exec_string = "`" + cmd + " > " + filename + "`" exec_string.gsub! '\\', '/' eval("#{exec_string}") uuid="" open(filename, "r:BOM|utf-16le:UTF-8") do |io| uuid = io.read end`

Thank you for the formatting. The splitted version works on PC, IE11, SU 2014.

my thinking is by having the full version open, you can choose to use the 'other' interpretation.. which may make it sightly more accurate? [image: for example...]

When it comes to push pull I understand that it does depend upon the winding (clockwise or counter clockwise) of the polygon. This is consistent and repeatable. However, with an extrusion that has a closed polyline as a path it is not repeatable. I can guarantee that the points for the face are always created exactly the same way - since they come out of a txt file. I store x and y points at 1/10000 decimal inches. The z values are set as 1/2 of the height of the door panel. I also calculate the path as x and y points which is a closed polyline. The Y values are 0. face = group.entities().add_face(face_pts) path = group.entities().add_curve(path_pts) face.followme(path) If I build the door at [0,0,0] look at it and then do a ctrl_z and repeat this process, I get a results where the the extrusion is sometimes reversed and sometimes not. It appears random - although the polyline and face are always created exactly the same way. When I create my curved stair stringers using fill_from_mesh I store each polygon's points with a clockwise winding. So far this has proved 100% predictable and repeatable. In the early days I used to do a lot of work with GIS and Windows GDI and create polypolygon this way. If you wanted to create a continent with a large lake that has an island that has a body of water you would have a series of 4 diminishing polygons each completely residing within each other. The outer most polygon would be clockwise (the continent) the large lake would be counter clockwise, the island would be clockwise and the body of water in the island would be counter clockwise. I found that the sketchup works essentially the same way with meshes.

http://www.sketchup.com/intl/en/developer/docs/ourdoc/ui#set_cursor http://www.sketchup.com/intl/en/developer/docs/ourdoc/tool#onSetCursor

I am not impressed with that book, at all. Using global variables is a no-no. Choose a name for your top level module, and write all your code within your own module namespace. Then use @vars (instance variables,) or @@vars (module variables.) Often we make each of our plugins in a sub-module of our toplevel author module.

@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!