@jean lemire said: Hi KSor, hi folks. There is no need for guide line or axes changes. See this SU file for ideas. Ha, ha, but Jean I beleave the problem is "how to slide along an edge tha is NOT parallel to one of the axes" - that's for the bolt. I beleave this "sliding along en edge" (if I only knew it !) can be used to move the arcs too. some minits later .... Oh, yeah I got it - that's better ! THX Jean !

You guessed right. "righty" refers to the up and down arrows and "rightx" refers to left and right arrows. If you plug in a joystick it will act in the same way. "lefty" refers to the keys "w" and "s" and "leftx" refers to "a" and "d" pretty cool huh? read the sketchy physics wiki and you will get your head around all of this in no time: http://sketchyphysics.wikia.com/wiki/SketchyPhysicsWiki

Thx to Aerilius - very usefull explanation !

Now you understand how to debug! Missing _item ... ...@KSORsubmenu.add**_item**... My typo - which occurs twice when the item is added to the submenu [or it wasn't thanks to the typing error ] Edit those two 'add' lines in your script and it should then work. I have edited the original post so other browsers won't get confused...

That's nice, Jeff. For me the only thing that's missing is a pic of the plane slicing the cylinder... to show the lack of continuity and stepping (which isn't cause you say it's a sine curve?). You sliced it and multiple copied it? Show it all, man, cylinder with multiple slicing planes. BTW, is that a dynamic component spinning or what?

@tig said: My "ArcCurve-set_segments" tool lets you change the segments of selected Arcs, just as you could using Enity Info on each one... you are also bound by the same limitations - e.g. you can't change the segments if the Arc is part of a 3d object... Argh, that's exactly what I was envisioning to do (a 3D object application). Well it makes sense that it cannot be done on the volume by changing the segments of the generating geometry. I didn't think of that. Thanks for the answers.

Position/rotate, then intersect two or more suitable forms, and finally erase unwanted parts to leave the required 3d solid. Reverse/orient the object's faces so all of them look outwards consistently... Use a group/component for these to avoid raw geometry clashes/sticking whilst positioning/rotating etc. [Edit: Dave has now added an example to his earlier post...] If you have v8-Pro there are native 'Solid' tools to simplify the adding/subtracting/trimming etc of forms. There are also a couple of 'Boolean' scripts to do similar work for 'Free' - one is free [by Oscar?] the other is inexpensive [available via Smustard.com?]...

@dan rathbun said: OH wait !! I'll fix the example. Sheesh that was a dumb one. (I had actually tested it with the "load on start" parameter, set to false. So this error did not happen for me in testing.) DONE Now I see the contours of a TEMPLATE for future plugins made in THE RIGHT WAY in a HURRY - that's good practice I think ! Still I have some claims and I'll try figure it out myself before I seek you help

I did put it in Ruby red to stress it was somehow 'special' without going into the added confusion of 'classes' - with an example to explain it too... OK it maybe ought to have a 'capital-letter', but we all say float not **F**loat quite a lot too without much of an issue ! But no dander is up [yet]...

You must uncheck "Use default value" first ... ADD: OR.. you can hilight "[Default]" at the top of the list, and change the default to what you want most of your code to do with TAB characters. Then change the specific few languages that you want to be different (ie: Python, Javascript, Java, HTML and CSS, all use 4 space tabs, instead of 2. Likely all the C language family as well. C, C++ and C#.)

Sorry, I don't quite understand your point... The tool initializes, it runs self.draw_pulley(), which runs self.dialog() and tests for the validity of its ' return'. If the user cancels the dialog ' nil' is returned and it stops. If the user enters valid inputs it returns ' true' and the remaining steps are executed to completion. If the user enters invalid input it then re-runs self.draw_pulley() [], which in turn runs self.dialog() and tests for its validity in its ' return' etc etc in a loop until either the user cancels or enters valid input... [ after it re-calls the method it immediately returns ' nil' to the previously executing version of the method, so that one goes no further] Note how two sets of references are taken from the ' results', one to test their validity and if OK then another @ set to be used in the next methods and also remembered for the next time... I left it this way because that's what you originally showed... personally I feel that a simple UI.messagebox("Values outside limits !\nExiting.") return nil would do, but at least this way the user does get chances to try again with a valid input in a new dialog - if they want to give up they can just cancel the dialog at any time...

@gaieus said: Try now. That's better - thx !

require 'sketchup.rb' This is cross-platform, not Windows only. It belongs at the top of the file. # pull in the standard API hooks. This NOT true. The API "hooks" are always loaded (if embedded Ruby is loaded,) by the Sketchup executable. (sketchup.exe) 'sketchup.rb' adds a few global methods like file_loaded() and file_loaded?(), and does not need to be required, unless you will use methods from that file, in the specific script, you are writing. You should read the "Tools/sketchup.rb' file to see what methods it has that you can use.

Welcome Keld. Nice to see you 'over here'... Post your questions in the Developers' forum.