![]() ![]() In the question's first picture, the initial gap which is displayed as 0", revealed itself to be a 1/64" gap when I cramped up the resolution in the "model info" pane. This photo was provided on the answer thread to display the behaviour: Faces are easier to click on, edges and corners being so thin and easy to miss with the cursor. I was initially moving the component by dragging its faces, which does move the object, but does not trigger the same "snapping" options on adjacent components. You can also drag the corner or edge instead of clicking and releasing, but the advantage of the click-move-click is that it will be easier to pan/zoom/rotate the camera while the selected component follows you around. The solution is to select the move tool ('m'), click a corner or an edge of one component, release, move the cursor until it snaps on the corner or edge it should connect to, and click again. I have simultaneously sought out help on a different forum, and received the following answer, which resolved the issue. Just in case, I'm showing a snapshot of my 'view' settings here: And I've tried moving the two pieces independently in the hope of "resetting" the grid, with no noticeable change. If I keep moving another notch, then the overlap is clear, confirming that the previous "notch" was as close as I could get it: If I move the horizontal piece closer to the vertical piece by "one notch", I still end up with a minute noticeable gap, but as the top image shows, its real measurement is 0": ), and objects seem to move in 1/16" increments. ![]() ![]() I'm using a grid that is 1/16" (the possible settings go as low as 1/64 But notice how the visible gap shows up as 0" N.B: I've added an arbitrary line, 3/8" apart, just for scale. If I move the objects as close as possible to one another, visually, and then use the measuring tool to confirm distances, I get a distance of 0" displayed, even though there is a clearly visible gap. How do I get objects to line up perfectly? screw threads, shoe sizes), the Options window may be more appropriate.I'm using the online free version of sketchup, and after adding several objects and moving them around, I can't quite seem to get two objects to line up (snap) exactly onto each other. This will depend on the context of the component - for "snap to grid" type functions, using the scale tool is usually most natural, whereas for "real world" objects that come in standard sizes (e.g. So, as you say, it is a matter of choosing one method or the other. But, to do that, you would still need to disable the scale tool completely, as there is no way to make the formula switch automatically between using the custom attribute when editing the window, or using current("LenZ") when you use the scale tool - it would require a function something like "Most_Recently_Changed(attr1,attr2)", which SU does not have (though it would be nice). You can create a custom "data entry" attribute to use in the Options window, and then reference that inside the formula. As soon as the user chooses a new value in the window, the literal value will replace the formula - leaving the snapping disabled. To use snapping from the Options it's best to use a drop-down list - if an attribute is using a formula, it cannot also be editable in the Component Options window. Goele wrote: So I figure that it is either one or the other. No matter what units you use for your drawing, current(), always return the length in inches! So if you are working in metric you may have to multiply the result by 2.54 before rounding. Here, if current("LenX") is over 25, you will get the result of the rounding functions, otherwise you get a fixed value of 25.Īnd there is yet another thing to be careful of. You could also use the functions ceiling() or floor(), if you want the snapping to always round up, or always round down - round() always goes to the closest one.Īlso, watch out for small lengths that might snap to zero length - the IF function can test for this, e.g. Note that you must wrap the parameter name in quotes as shown here. In reality, this kind of error is trapped, but still gives strange results. ![]() doesn't know when to stop calculating, because every change to LenX makes it change again, and again - a circular reference. For this, you need the special function "current()".Ĭurrent() receives a value from your mouse (or VCB) interaction, and then makes the DC equations update once, and only once. The maths to do this is relatively simple - divide by your "snap unit", round to an integer, then multiply up again by the snap unit.īut first, you need to know about the way that new values get updated from the user interface. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |