Can I deactivate "constrained on....."?
-
As Dave said, there is no way to deactivate the behavior with native SU Tool.
However, if this is about Drawing line, you can use FredoTools::DrawAlong. There is an option to draw 'free', with Alt modifier.
And, if you move object, FredoTools::MoveAlong has the same option.
Fredo
-
The inferencing system is a feisty beast, but if you can learn to work without fighting it then you'll find it a lot easier. Personally, I'd solve this problem by drawing the line to a random point in space, then using the move tool to drag the endpoint to where it needs to be.
-
Fredo;
The biggest problem I have with your fantastic toolset(s) is remembering the tool is there!!!All of your tools lie on the bottom of my screen, taking the whole width.... there are so many. Curviloft is the one I use by far the most. Can't live without it.
I will endevour to start investigating and using the others more.
-
oceanembers
I usually end up doing just that, but it gets tedious. -
SketchUp's inference engine constantly guesses what you are trying to accomplish and prefers a particular snap based on its best guess. Sometimes that guess is not the snap you wanted, especially when there are alternatives very close together. As you note, the result can be quite frustrating.
You have to help the inference engine by doing something that steers its guess to what you really wanted. Obviously one approach is to zoom in close enough that the difference between the possibilities is very clear, but clipping can make this non viable and increased sensitivity of the cursor when zoomed in tight can make it difficult to control. Another approach is to hover the cursor over something that gives the inference engine a clue about what you really want, for example hovering over an edge until the "on edge" tip shows. But the inference engine sometimes determinedly goes for a different snap even after you try to help it. This behavior is why ability to turn off snaps is a very frequent feature request.
-
slbaumgartner
But the inference engine sometimes determinedly goes for a different snap even after you try to help it. This behavior is why ability to turn off snaps is a very frequent feature request.
I did ask for this many years ago...... More than once, but to no avail.
SU users seem to have better luck at seeing a new feature they suggested than seeing a fix to something they suggested.
-
@jgb said:
SU users seem to have better luck at seeing a new feature they suggested than seeing a fix to something they suggested.
Yeah, both feature requests and bug reports vanish into the Trimble jungle, many of them never to be seen again. We all know that the development team is resource limited, but they have never revealed how they choose priority among the many items.
-
"Failure to fix" has been endemic to the SU development team far longer than Trimble.
Look how long it took the team to start SU in pointer mode (select) rather than draw mode.
I had to use an independent Ruby script fix for years before SU finally fixed it. -
Wo3Dan
Good idea, good thing I thought of it
I will try that next time it happens.
Thanks. -
@jgb said:
Whenever I draw a line that is just slightly off (by design) the red, green or blue global axis, SU snaps the endpoint just off my mark with the "Constrained by..." message, and won't let me move it.
As mentioned in your other thread where you wanted to change the bounding box and component axes to run along the component's geometry, you can take away the disturbing factor by temporarily redrawing the axes. Then snapping to your target shouldn't be a problem.
If this happens a lot, create a scene with only the "odd" drawing axes saved.
p.s. it is important to know that the use of the scene with its saved axes is not restricted to just one context. Open a (nested) group or component and you'll still be able to use the scene!
Advertisement