The function that allows you to select and transform objects with one single click feels problematic

[zhuluyao2011]

When any transform tool is active, I click on the screen but it transforms an unintended object that happened to be where my mouse was hovering, even if I have already selected another object that I intended to apply this transformation to.

I think this function is designed to reduce the need to repick tools, but I found this function very unlikely to be helpful in a CAD software, because there are too many elements on the screen and overlaying. I would rather turn this function off at all times.

[Fausto_Brevi]

Maybe this slide from one of my lesson could be helpful.

[zhuluyao2011]

Thank you for the reply. The slide you attached is very helpful in clarifying the scenario that I was describing.

Taking the two Approaches in the attachment for example, I found the vast majority of times in actual design practices, I am using Approach 1 to transform objects. And Approach 2 is acting almost like a malfunction that I would like to avoid 99% of time.

I can think of two reasons causing Approach 2 to be unnecessary:

1.

In CAD design pracitce, there is not many cases when the same tranformation command will be applied continously across multiple objects in a row, which is what Approach 2 is designed for.

The more realistic scenario is that one object will be moved to a certain location, followed by other types of transformation until this object is in a relatively precise state of design, before another object will be selected and applied a combination of various transformations to, which is what Approach 1 is design for.

2.

Most of the times, CAD design is around localized details, which leads to the fact that the camera will be zoomed in to smaller parts within a bigger assembly. The rest of the screen will be filled up by the rest of the assembly and ussually there is no "empty space" as described in the attachment on the screen to execute the step of click&drag in Approach 1, because it will very likely to accidentally trigger Approach 2 if any surrounding object is clicked on.

[Fausto_Brevi]

Try to use the Transform manipulator instead (see attached image).

Maybe it could fit better in your workflow.

[zhuluyao2011]

Yes, Transform Manipulator is also the tool I use to prevent such error in some cases. 

The benefit of the Manipulator regarding this issue is that by clicking on the handles of the manipulator, user can avoid accidentally clicking on unintended objects.

The limitation of using the Manipulator includes:

1.

Having to aiming for the handles with cursor, which takes more time and effort than Approach 1.

2.

When using snapping along with the Manipulator, user still needs to click near something as a snapping target outside of the handles. And if accidentally clicking on an unintended object in this step, the Manipulator tool will execute such transformation on the unintended object, leading to the same issue that Approach 2 causes.

[Fausto_Brevi]

What else can I say? I can only say that there is no software interface that you can love 100%. For example, I personally dislike those software that deselect everything by clicking in an empty space, but if I need them I use them anyway. It is not so easy to change the workflow of an interface: the risk is to lose most users without still being able to satisfy everyone. Bye