Topics created by jumpjack

@JitendraG I would hope so. I did speak with Anton a few weeks ago to get Clothworks and Fullscreen sorted for 2024.

Physics is not as quick to revive because it is a complete rewrite to make it compatible. He also has a fulltime job and life to contend with.

@unknownuser said:

but how to join such objects into a working mechanis.

What sort of mechanism?
there are infinities! 😄

http://www.youtube.com/watch?v=KdtYVq5f70Q&list=PLAD82B42694971FB7

http://www.youtube.com/watch?v=UOzrGRHAFdA&feature=c4-overview-vl&list=PLAD82B42694971FB7

http://www.youtube.com/watch?v=Fd9W89hpm9U&list=PLAD82B42694971FB7

and you can put squares wheeles if you want! 😉

etc...

http://www.youtube.com/watch?v=HeN46aFhnkU&list=PLAD82B42694971FB7

http://www.youtube.com/watch?v=mXpfO9WhlPA&list=PLAD82B42694971FB7

Some folks like to use a Wacom tablet and some like the fancy mice with lots of buttons. I've tried running SketchUp on my Cintiq and with several different fancy mice. The fancy mice are in their boxes and the Cintiq is reserved for other things like photoshopping drawings. I like my inexpensive 3-button mice for drawing in SketchUp. When it comes down to it, the tools in the program are all just single point sorts of things. You draw an edge or click on something. For my money the CMB coupled with Shift work just fine for navigating around the model.

Do you know about groups and components?

"Zoom to extent", or how it's named in English, solved the problem. 😄

The tiny facets failing to form issue is down to SketchUp's built-in tolerance.
Every modeling application must have such settings, because calculating the numbers used for points will inevitably result in some numbers that are not exactly identical BUT ought to be considered identical. Otherwise you'd snap to a vertex and the application would recognize the existing vertex point and the snapped point as being almost identical, but not quite, if there even a zillionth of an inch difference in one value from the Maths...
So the tolerance used is a thousandth of an inch.
SketchUp works in inches even when the Model Units are say mm.
The 'displayed units' are just for user's convenience.
Edges less that ~0.25mm will therefore often fail to form as the two vertices forming the tiny edge's ends are deemed to be coincident, and you can't make a 0 length line ! Without the missing edge a face can't get made because it needs a continuous loop and the tiny gap thwarts that !
I expect that 1/1000" was chosen because SketchUp is intended for modeling buildings and their parts, furniture etc, and 1/1000" is far more accurate that you'll ever need.
With the advent of 3d printing and related solid-modeling many parts are smaller, and/or modeled to an accuracy that was never originally envisaged when SketchUp was first developed.
Therefore, if you model at x100 or x1000 you should avoid the tiny face issue.
Set your Model Units to meters, at 3dp without any length snapping or unit display set.
Now model.... typing in 10 as if it were mm, when it's actually 10m...
Never add a units suffix to your input.
When your modeling is finished and saved, draw a line 10 long, then use the tapemeasure tool and pick the two ends of that line, the VCB says 10.000, immediately type 10mm [note the units suffix mm]... and answer Yes when asked if you want to scale the model. It now shrinks by 1/1000 - Change your Model Units to mm. All really tiny facets will continue to exist; as was said they can exist it's their initial creation that is the issue.

@azuby said:

Use an instance variable. At the moment, your code should be in a class. Initialize your instance variable (i. e. @clicks - the @ is neeeded) in the initialize method of your class and use the variable in the code which is executed by clicking on your button.

azuby

Thanks, but this is too complex for me, I started studying Ruby yesterday, I'm still at "copy&modify&paste" level... 😒

This is my source:

def MoveLeft model = Sketchup.active_model entities=model.active_entities sp=entities[1] plane=sp.get_plane pos += 1 plane=[Geom;;Point3d.new(pos,0,0),Geom;;Vector3d.new(1,0,0)] sp.set_plane plane end def MoveRight model = Sketchup.active_model entities=model.active_entities sp=entities[1] plane=sp.get_plane pos -= 1 plane=[Geom;;Point3d.new(pos,0,0),Geom;;Vector3d.new(1,0,0)] sp.set_plane plane end pos=0 toolbar = UI;;Toolbar.new "Sections" cmdSectionLeft = UI;;Command.new($tStrings.GetString("Test")) { MoveLeft } cmdSectionLeft.tooltip = $tStrings.GetString("Move section to left") cmdSectionLeft.status_bar_text = $tStrings.GetString("Move section to left") cmdSectionLeft.menu_text = $tStrings.GetString("Move left") toolbar = toolbar.add_item cmdSectionLeft cmdSectionRight = UI;;Command.new($tStrings.GetString("Test")) { MoveRight } cmdSectionRight.tooltip = $tStrings.GetString("Move section to Right") cmdSectionRight.status_bar_text = $tStrings.GetString("Move section to Right") cmdSectionRight.menu_text = $tStrings.GetString("Move Right") toolbar = toolbar.add_item cmdSectionRight toolbar.show

How do I hold value for I among various button presses?

thanks a lot, I'll try it.