Skip to content

Translation (and other transformations') behavior on (un)selected objects #459

@anusser

Description

@anusser

Disclaimer: This issue is more thought of as a point of discussion rather than a feature request. What I suggest is a different behavior that subjectively is more intuitive to me, but it is an opinion and I open this issue to see whether more people see it that way. I already know that some people I talked to prefer a different behavior than what is currently the case.

Currently, when being in translation mode and the cursor is far from the object that is selected, then a closer object is selected and translated instead, as described in the manual. This behavior can be quite frustrating, e.g., trying to translate a circle having the cursor on its center often does not translate the circle but another object that is close to the center.

There are two ways to avoid the behavior in the above example:

  1. Do not only consider the boundary of the circle but also the interior when deciding which object to translate.
  2. Change the behavior of translation mode.

I would go for the second option, and I suggest the following change:

  • If an object is selected in translation mode, then always translate this object.
  • If no object is selected, then translate the closest object to the cursor (which is already the case I believe); However, do not select the object that is being translated.

Like this, one can translate a lot of different objects without exiting translation mode, but one can still get the (subjectively) expected behavior if an object is selected. The same of course also applies to rotation, etc.

What do you think?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions