This will let you use the debugging functionality of IDEs/editors that support the Ruby Debug protocol: To make debugging SketchUp Ruby extensions easier we have a Ruby debugger interface that can be added to your SketchUp installation. SketchUp/ruby-c-extension-examples Debugging We provide examples on how to create Ruby C Extensions that work with various SketchUp versions and platforms: This allows for more complex functionality and possible performance improvements. Ruby itself allows you to work with Ruby code via C (and C++). SketchUp/sketchup-ruby-api-tutorials Ruby C Extensions within SketchUp These will take you through various common scenarios and concepts of the SketchUp API. To get you started we have a collection of examples of tutorials. For more information refer to the LayOut API Overview.Ĭurrently the LayOut Ruby API is only available from SketchUp. LayOut APIĪs of SketchUp 2018 you can also create and manipulate LayOut documents. Visit our SketchUp Developer Center for more information and resources on SketchUp's APIs. It is available from within SketchUp, it cannot be used by itself. In any case we’re working on some additional tools and fixes to make sure if anything gets disconnected it will be easy to reconnect or recreate.The SketchUp Ruby API allows you to interact with SketchUp models and the SketchUp application. In a worst case scenario, if an opening stops being dynamic, for what ever reason (accidental exploding, or some unexpected bug) erasing the opening and re-placing a new window component will take no more than 2-3 seconds… so it’s usually no big deal.

If the model were then saved and sent back to you, the opening will become dynamic again as long as the original component it was connected to is still there, and not totally deformed. WallCutter (Not released yet!) - An opening will stay where it’s supposed to be and it will not be dynamic, just like you’re used to today.

Zapper completely strips a dynamic component from its dynamic behaviors so all the components will be turned to regular components. If the possible jumbling is a problem (it rarely is I believe), one could explode them or you could zap the components with the Zapper tool that comes with FlexTools, before sending. If the model were returned to you, the components would keep working as usual. If that someone were to try and scale them, they would possibly jumble up, or not do anything. If you were to share a model with someone who doesn’t have FlexTools and WallCutter installed:įlex components - Would stop being dynamic.

Flextool sketchup