Copy/Paste Behavior in Viewport #79733

New Issue

Leo Schmidt · 2020-08-12T13:13:24+02:00

Leo Schmidt commented

2020-08-12 13:13:24 +02:00

System Information
Operating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon R9 M390 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.15

Blender Version
Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-08-10 21:16, hash: acd4687063
Worked: Never worked in 2.8+

Short description of error
When pasting an object, the gizmo is not positioned at the newly created object, where you would expect it to be. Instead, there are two cases - both seem to be not intended.
The pasted object also is not active for direct manipulation despite the visual indication with the gizmo.

Exact steps for others to reproduce the error
If there is a selection somewhere else before pasting, the gizmo ends up in the wrong position. Example:

If there is no selection before pasting, there is no gizmo appearing at all. Example:

A directly interconnected problem is that pasted objects are not made active despite having an attached Gizmo. Example:

Potential fix

The gizmo could always appear and show where the object is pasted (belonging to the new object).
The pasted object could become active. When multiple objects are pasted, the selection and active states of the copied objects could be transferred to the newly pasted ones. Also, all previous selections could be deselected after pasting.

Thank you :)

**System Information** Operating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits Graphics card: AMD Radeon R9 M390 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.15 **Blender Version** Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-08-10 21:16, hash: `acd4687063` Worked: Never worked in 2.8+ **Short description of error** When pasting an object, the gizmo is not positioned at the newly created object, where you would expect it to be. Instead, there are two cases - both seem to be not intended. The pasted object also is not active for direct manipulation despite the visual indication with the gizmo. **Exact steps for others to reproduce the error** If there is a selection somewhere else before pasting, the gizmo ends up in the wrong position. Example: ![image1.jpg](https://archive.blender.org/developer/F8772919/image1.jpg) If there is no selection before pasting, there is no gizmo appearing at all. Example: ![image2.jpg](https://archive.blender.org/developer/F8772923/image2.jpg) A directly interconnected problem is that pasted objects are not made active despite having an attached Gizmo. Example: ![image3.jpg](https://archive.blender.org/developer/F8772942/image3.jpg) **Potential fix** 1. The gizmo could always appear and show where the object is pasted (belonging to the new object). 2. The pasted object could become active. When multiple objects are pasted, the selection and active states of the copied objects could be transferred to the newly pasted ones. Also, all previous selections could be deselected after pasting. Thank you :)

Leo Schmidt commented

2020-08-12 13:13:24 +02:00

Added subscriber: @LeoSch

Philipp Oeser commented

2020-08-13 12:23:05 +02:00

Added subscribers: @WilliamReynish, @ideasman42, @lichtwerk

Philipp Oeser commented

2020-08-13 12:23:05 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Philipp Oeser commented

2020-08-13 12:23:05 +02:00

Pasted objects are selected but not active, editing in the properties Editor is for the active object. So far this is by design.
Looks like the gizmo should actually stick to selected objects (not active, but unselected)

So in this regard, I can confirm:

- If you copy, move active, then paste, original object stays active but gets unselected (I'd say this is expected), gizmo should hop to selected (new object), looks like an update is missing
- If you copy, paste right away (like in your last picture), the gizmo will actually hop to the new pasted object (I'd say this is expected), editing in the Properties editor is still for the active (old) object [while this might sound strange, I'd say this is still expected]

Regarding your potential fixes: these might be improvements, but would need proper design decissions from the UI team (but these would not be considered a bug)

I would still confirm this for now because of the inconsistency between - [x] and - [x] (or rather the potential bug / missing update in [1]).

CC @ideasman42
CC @WilliamReynish

Pasted objects are selected but not active, editing in the properties Editor is for the active object. So far this is by design. Looks like the gizmo should actually stick to selected objects (not active, but unselected) So in this regard, I can confirm: - - [x] If you copy, move active, then paste, original object stays active but gets unselected (I'd say this is expected), gizmo should hop to selected (new object), looks like an update is missing - - [x] If you copy, paste right away (like in your last picture), the gizmo will actually hop to the new pasted object (I'd say this is expected), editing in the Properties editor is still for the active (old) object [while this might sound strange, I'd say this is still expected] Regarding your potential fixes: these might be improvements, but would need proper design decissions from the UI team (but these would not be considered a bug) I would still confirm this for now because of the inconsistency between - [x] and - [x] (or rather the potential bug / missing update in [1]). CC @ideasman42 CC @WilliamReynish

Leo Schmidt commented

2020-08-13 13:36:03 +02:00

Thanks for the investigation into this issue.

Pasted objects are selected but not active, editing in the properties Editor is for the active object. So far this is by design.

I was bringing this up because it is inconsistent with the duplication behavior.
Users would probably expect the same behavior when copy/pasting and duplicating.

Pasted objects don't become active
Duplicated objects become active (which subjectively seems correct)

Thanks for the investigation into this issue. > Pasted objects are selected but not active, editing in the properties Editor is for the active object. So far this is by design. > I was bringing this up because it is inconsistent with the duplication behavior. Users would probably expect the same behavior when copy/pasting and duplicating. - Pasted objects don't become active - Duplicated objects become active (which subjectively seems correct)

Philipp Oeser commented

2020-08-13 13:42:21 +02:00

In #79733#995454, @LeoSch wrote:
I was bringing this up because it is inconsistent with the duplication behavior.
Users would probably expect the same behavior when copy/pasting and duplicating.

Pasted objects don't become active

Duplicated objects become active (which subjectively seems correct)

I would agree here (there might be cornercases to check -- but to me, this would seem to work better, yes).
Point is, that this would not be a bug, but more of a request for improved behavior [which we usually dont handle here on the bugtracker]

> In #79733#995454, @LeoSch wrote: > I was bringing this up because it is inconsistent with the duplication behavior. > Users would probably expect the same behavior when copy/pasting and duplicating. > > - Pasted objects don't become active > - Duplicated objects become active (which subjectively seems correct) I would agree here (there might be cornercases to check -- but to me, this would seem to work better, yes). Point is, that this would not be a bug, but more of a request for improved behavior [which we usually dont handle here on the bugtracker]

Philipp Oeser commented

2020-08-13 14:09:44 +02:00

Let me add that the operators select option doesnt seem to work:

Let me add that the operators `select` option doesnt seem to work: ![image.png](https://archive.blender.org/developer/F8776832/image.png)

Philipp Oeser commented

2020-08-13 14:38:21 +02:00

In #79733#995473, @lichtwerk wrote:
Let me add that the operators select option doesnt seem to work:

Well OK, this doesnt clear the BASE_SELECTED flag in add_loose_objects_to_scene if it was selected before (when copying).
And tbh, it doesnt promise to deselect if this option is not set.
There might be reasons to do it like this, but was confusing for me...

(Note: copying unselected objects is possible e.g. from the Outliner if objects are selected there [without the Sync Selection option] -- for those kind of unselected objects, the Select option of the Paste operator actually works...)

> In #79733#995473, @lichtwerk wrote: > Let me add that the operators `select` option doesnt seem to work: > ![image.png](https://archive.blender.org/developer/F8776832/image.png) Well OK, this doesnt **clear** the `BASE_SELECTED` flag in `add_loose_objects_to_scene` if it was selected before (when copying). And tbh, it doesnt promise to `deselect` if this option is not set. There might be reasons to do it like this, but was confusing for me... (Note: copying unselected objects is possible e.g. from the Outliner if objects are selected there [without the `Sync Selection` option] -- for those kind of unselected objects, the Select option of the `Paste` operator actually works...)

Hans Goudey commented

2020-09-09 00:16:18 +02:00

Added subscriber: @HooglyBoogly

Hans Goudey commented

2020-09-09 00:16:18 +02:00

We have another report about gizmos not properly updating there location when selection changes here: #76335 (After switching to Tweak tool its gizmo appears in center of previously selected area.)

I don't have the energy to dive into that code right now though.

We have another report about gizmos not properly updating there location when selection changes here: #76335 (After switching to Tweak tool its gizmo appears in center of previously selected area.) I don't have the energy to dive into that code right now though.

Chris Kohl commented

2020-09-13 22:10:21 +02:00

Added subscriber: @ckohl_art

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Copy/Paste Behavior in Viewport #79733