Fix move tool and shift to constrain axis function

[samuel.carslake]

I cannot be the only one who is frustrated endlessly at the "constrain" option when using the move tool. It currently constrains as long as you don't move your cursor over 45 degrees off the axis you're trying to move something on. Which honestly is rather useless given that objects are often beyond this line when attempting to move an object, and then revit snaps to the alternative axis when moving. 

To further add to this, the align tool does not suffice in for this function, as it will not work for groups of objects at a time. Additionally, if you're using the align tool on single objects it does not behave consistently for it to be effective, ie: it modifies edges and endpoints of objects differently when you select them.  

Most other cad programs have this feature. I'm at a bit of a loss as to why revit can't perform this function. 

[BIMBenHL]

My apologies if you're already aware of the following tip and it doesn't help you:

When aligning, once you have selected your reference point/plane, if you hold the Ctrl key on your keyboard before selecting each new element to align to your reference, it'll retain the reference for the next aligning rather than reset it.

Holding the Shift key while performing a Copy or Move (or other) command will temporarily untoggle the Constrain feature for the duration of the key hold. So if you have Constrain ticked it will toggle it off, and if you have it unticked, it'll toggle it on. That being said, how would you like the behaviour of an orthogonal constrain to work if not to change to a new direction when you move your cursor past the 45 degree angle towards that direction? This current behaviour is the only sensible way I can see it behaving.

[samuel.carslake]

Thanks for the tip! I don't see the align tool behaving in the same way unfortunately as its a bit more versatile in nature. So it often doesn't overlap with when you definitively want something to be "moved" and not stretched or altered. But this will be helpful nonetheless. 

The way I would expect the move tool to work is that it constrains an object along the axis you move it on regardless of how far away from the objects original origin/axis you move your cursor. 

This functionality is the most predictable way you can expect something to move when drafting. If the axis that an object is constrained to is adjusted on the fly then it becomes incredibly frustrating to align it to other things that may happen to be greater than 45 degrees away from the origin of the move.

In other words, its impossible for the program to predict the proximity of the destination of a move command, therefore it should give users the control necessary to perform that command consistently. 

Furthermore, if the feature is called "constrain" and it changes based on cursor direction once it has begun dragging, then by definition it has not constrained at all. 

Please let me know if any of that isn't clear. All I can see on forums for when people need to do this is that people draw temporary detail lines to get the snaps they require, or perform two move commands along each axis, which poses its own risks with walls auto joining each other before the second command etc. 

Thanks for the reply!

[BIMBenHL]

Hi Sam

Thanks for the tip! I don't see the align tool behaving in the same way unfortunately as its a bit more versatile in nature. So it often doesn't overlap with when you definitively want something to be "moved" and not stretched or altered. But this will be helpful nonetheless. 

---

It sounds like sometimes you ought to be using the trim/extend command? Or perhaps the Extend Multiple?

Furthermore, if the feature is called "constrain" and it changes based on cursor direction once it has begun dragging, then by definition it has not constrained at all. 

---

This makes it sound like you're not using the move command at all, but instead clicking, holding the click and dragging an element?

Even so, everything you've said sounds like you expect Revit/the element to know it should be constrained to a single axis? Much like an electrical fixture (or any face(?) based element) when placed on a wall? You're only ever able to drag it around that wall surface and not away from it.

If I have that right, what is it that should tell something that isn't hosted in this way which axis it should be constrained by? Not everyone has precise control of their hands when clicking, but are we suggesting that the initial mouse movement after confirming which elements are to be included in the Move command is the axis/direction in which you want to move the element? I personally would despise this behaviour.

From the way I have interpreted your message, you want to fix something which I don't view as broken. Instead, you're suggesting a different behaviour which I would welcome the option of having, but preferably not as a default.

If you are so far from an element and so close to the 45 degree threshold, is this perhaps user error?

Apologies if I've misunderstood anything you've said!

[adrianJATDT]

I am also having this problem. It is not user error when the reference object is more than 45 degrees away from the move plane! For example I am trying to copy an item to a new corner in the bedroom, along a straight line, but to line up with another object in the opposite corner of the room. When I try to hover my mouse to reference this opposite point, the move command automatically snaps away from my intended straight line movement.

For example in ArchiCAD, we can move/copy items with a single direction locked in during the command, hovering to points anywhere on the plan to reference to. This does not exist in Revit, without drawing extra reference lines all over the plan, very frustrating and time consuming.