Add smart behavior (linking/instanciation) when pasting a collection in the Outliner or the 3DView #69393

Open
opened 2019-09-01 23:41:27 +02:00 by SABRI Salim · 18 comments

System Information
Operating system: Linux-4.15.0-55-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.26

Blender Version
Broken: version: 2.81 (sub 4), branch: master, commit date: 2019-09-01 07:31, hash: ae43b1d51b
Worked: Never

Short description of error
Copied Collection does not paste correctly in the Outliner

Exact steps for others to reproduce the error
Copy a Collection from the Outliner and Past it in the Outliner - Collection doesn't shown in the 'View Layer' but in 'Orphan Data'

**System Information** Operating system: Linux-4.15.0-55-generic-x86_64-with-debian-buster-sid 64 Bits Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.26 **Blender Version** Broken: version: 2.81 (sub 4), branch: master, commit date: 2019-09-01 07:31, hash: `ae43b1d51b` Worked: Never **Short description of error** Copied Collection does not paste correctly in the Outliner **Exact steps for others to reproduce the error** Copy a Collection from the Outliner and Past it in the Outliner - Collection doesn't shown in the 'View Layer' but in 'Orphan Data'
Author

Added subscriber: @Dalkoom

Added subscriber: @Dalkoom
Author

The Bug Is still here

The Bug Is still here
SABRI Salim changed title from Copy Past in the Outliner to Copy Past Collection in the Outliner 2019-09-09 22:59:54 +02:00
Dalai Felinto changed title from Copy Past Collection in the Outliner to Copy Paste Collection in the Outliner 2019-09-17 19:06:58 +02:00

Added subscribers: @WilliamReynish, @natecraddock, @dfelinto

Added subscribers: @WilliamReynish, @natecraddock, @dfelinto

@Zachman is this something you would be interested on?
@WilliamReynish do we have a clear design on what to do here? It seems that copy/paste for collections is undefined everywhere (e.g., in the viewport is simply paste the objects)

@Zachman is this something you would be interested on? @WilliamReynish do we have a clear design on what to do here? It seems that copy/paste for collections is undefined everywhere (e.g., in the viewport is simply paste the objects)

@dfelinto indeed we should make copy/paste work correctly for Collections in the Outliner. I can’t imagine we’d need a whole design task for it, is there anything that isn’t clear here?

@dfelinto indeed we should make copy/paste work correctly for Collections in the Outliner. I can’t imagine we’d need a whole design task for it, is there anything that isn’t clear here?

Added subscriber: @brecht

Added subscriber: @brecht

@WilliamReynish what is not clear:

  • What do we expect when copy/paste in outliner?
    My suggestion: We copy the collection and add it inside the current selected collection?

  • What do we do when copy in outliner but paste in viewport?
    My suggestion: Instance the collection

I'm not strongly committed to either suggestion just the first thing that came to my mind. @brecht any 2 cents?

@WilliamReynish what is not clear: * What do we expect when copy/paste in outliner? *My suggestion: We copy the collection and add it inside the current selected collection?* * What do we do when copy in outliner but paste in viewport? *My suggestion: Instance the collection* I'm not strongly committed to either suggestion just the first thing that came to my mind. @brecht any 2 cents?

@dfelinto I'm willing to look at this, and I think instancing on paste in the viewport makes sense, though I imagine a paste in the outliner would duplicate the collection on the same level as the copied collection.

@dfelinto I'm willing to look at this, and I think instancing on paste in the viewport makes sense, though I imagine a paste in the outliner would duplicate the collection on the same level as the copied collection.

@dfelinto the seems entirely reasonable.

@dfelinto the seems entirely reasonable.

(...) paste in the outliner would duplicate the collection on the same level as the copied collection.

This is already covered by duplicate. If you copy from a .blend file and paste in another this won't work.

The way I see working elsewhere is to paste in the same level as the current selected element (which by the way is a great concept to determine what is the active collection when not explicitly selecting it).

> (...) paste in the outliner would duplicate the collection on the same level as the copied collection. This is already covered by duplicate. If you copy from a .blend file and paste in another this won't work. The way I see working elsewhere is to paste in the same level as the current selected element (which by the way is a great concept to determine what is the active collection when not explicitly selecting it).

Added subscriber: @ChristophWerner

Added subscriber: @ChristophWerner

This comment was removed by @ChristophWerner

*This comment was removed by @ChristophWerner*

In my opinion this confuses the user. I know the intention behind it to differ between the current focus (Outliner or Viewport) and do somethings that "may" be interesting for the user.
In your case: Make an instance when the viewport is focused and a copy when the outliner is focused.

But I think it would be better to simply do what what the user expects behind a command.

So my proposal for the commands and the results:
"Copy command" -> Copy a collection / an object and Paste it as a real duplicate(a copy).
"Link/Instance" command -> Make a linked version of the collection / or an Instance an object, when the user Paste it into the target.

Please don't do something that is different to the command.

In my opinion this confuses the user. I know the intention behind it to differ between the current focus (Outliner or Viewport) and do somethings that "may" be interesting for the user. In your case: Make an instance when the viewport is focused and a copy when the outliner is focused. But I think it would be better to simply do what what the user expects behind a command. So my proposal for the commands and the results: "Copy command" -> Copy a collection / an object and Paste it as a real duplicate(a copy). "Link/Instance" command -> Make a linked version of the collection / or an Instance an object, when the user Paste it into the target. Please don't do something that is different to the command.

Added subscriber: @dr.sybren

Added subscriber: @dr.sybren

This is a similar issue to #73197 (Collections created with CTRL G do not appear in Outliner View Layer) and #53662 (Usability issues with old group operators).

This is a similar issue to #73197 (Collections created with CTRL G do not appear in Outliner View Layer) and #53662 (Usability issues with old group operators).

This is the kind of thing that @Zachman may be interested/persuaded to look at.

This is the kind of thing that @Zachman may be interested/persuaded to look at.

Added subscriber: @mont29

Added subscriber: @mont29

This is really not a bug at all, copy/paste is working as expected. Adding smart behavior when pasting a collection is for sure a nice TODO, but there is no bug in current behavior.

This is really not a bug at all, copy/paste is working as expected. Adding smart behavior when pasting a collection is for sure a nice TODO, but there is no bug in current behavior.
Bastien Montagne changed title from Copy Paste Collection in the Outliner to Add smart behavior (linking/instanciation) when pasting a collection in the Outliner or the 3DView 2020-02-19 15:34:47 +01:00
Philipp Oeser removed the
Interest
Pipeline, Assets & IO
label 2023-02-10 08:54:20 +01:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
7 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#69393
No description provided.