Components are a lot like Groups, but with a handy twist: copies of Components are related together, so changes you make to one are automatically reflected in all the others. Groups and Components: Build smarter modelsīy "sticking together" parts of the geometry in your model to make Groups, you can create sub-objects that are easier to move, copy and hide. You can use SketchUp's Paint Bucket tool to paint your model with materials like colors and textures. You can even use Follow Me to round off (fillet) edges on things like handrails, furniture and electronic gadgets. Create a bottle by drawing half of its outline, then using Follow Me to sweep it around a circle. Model a bent pipe by extruding a circle along an L-shaped line. You use SketchUp's innovative, do-everything Follow Me tool to create 3D forms by extruding 2D surfaces along predetermined paths. If you want, you can print scaled views of your model, and if you have SketchUp Pro, you can even export your geometry into other programs like AutoCAD and 3ds MAX.įollow Me: Create complex extrusions and lathed forms When you're ready, you can build models that are as accurate as you need them to be. Because you're working on a computer, everything you create in SketchUp has a precise dimension. SketchUp is great for working fast and loose in 3D, but it's more than just a fancy electronic pencil.
SketchUp is known for being easy to use, and Push/Pull is the reason why.Īccurate measurements: Work with precision Want to make a window? Push/Pull a hole through your wall.
Or draw the outline of a staircase and Push/Pull it into 3D. You can Push/Pull a rectangle into a box. Just click to start extruding, move your mouse, and click again to stop. It's as simple as that.Įxtrude any flat surface into a three-dimensional form with SketchUp's patented Push/Pull tool. To build models in SketchUp, you draw edges and faces using a few simple tools that you can learn in a small amount of time. For example, a rectangular face is bound by four edges that are connected together at right angles. Edges are straight lines, and faces are the 2D shapes that are created when several edges form a flat loop.
What is needed here is a entity identifier which include the "path" to get to the entity, so it truly represents a single unique entity in terms of the display.Developed for the conceptual stages of design, SketchUp is a powerful yet easy-to-learn 3D modeling software tool that combines a simple, yet robust tool-set with an intelligent drawing system that streamlines and simplifies 3D design.Įdges and Faces: That's all there is to itĮvery SketchUp model is made up of just two things: edges and faces. As I drill down through the database and think I am pointed at a single, unqiue entity, I am often pointed to an entity in a component definition, which, if the component is used more than once may be in hidden instances of the same component, instances of the component which are on layers which are off, as well as in an instance which is visible. However, as I write this I see that part of the problem is what is meant by an entity. The last two are pie-in-the-sky, but the first one would be a useful function.
However, it would be nice if they added 1 to 3 of these new functions:Įntity.is_visible? - not hidden, and not on a layer which is hidden (including groups and sub-components which are hidden or on layers which are hidden)Įntity.is_in_current_view - is_visible? and also is visible in current camera viewĮntity.is_obstructed - is visible? but is behind something else which is not transparent. MartinRinehart wrote:Any reason not to declare visible? a bug?Īt this point, if they some changed what it meant, it would break any scripts which were using it to mean "not hidden". #printf("is_enitity_visible_in_sketchup: %s return true\n", ) # Layer0 is only invisible at the top level #printf("is_enitity_visible_in_sketchup: %s\n", ) In included both entity.hidden? and !entity.visible? - which is probably redundant.Ĭode: Select all def is_enitity_visible_in_sketchup(entity) It gets tricky because an entity in a nested group/component is invisible of any of the layers of the parents is off, (except for Layer0 which is always on in a component or group even if it is off at the top level). I wrote this routine to determine if an entity is truly visible. If e is on an invisible layer I'd like e.visible? to report false, no? MartinRinehart wrote:Did a quick test: e.visible? reports true when e.hidden? reports false.