Make Single User operation ignores linked data-blocks. #91410

Closed
opened 2021-09-14 16:56:09 +02:00 by Bastien Montagne · 8 comments

Currently Make Single User operation (from the Object -> Relations 3DView menu e.g.) explicitly ignore any linked ID.

From code history this seems to have been the behavior since a very long time (earliest commit I could find is from 2012 by @ideasman42 , but it's only a cleanup one...). @brecht, @ideasman42, do you guys know why this is the current behavior?


This was reported as an issue by @JulienKaspar in this usecase:

  • Having several local objects using a same linked obdata.
  • If you want to get local single users duplicates of those obdata for some of those objects, you currently have to manually click on the 'user number' button in object data properties ID template for each of the objects.
  • Ideally you should be able to select desired objects in the 3DView, and just run 'Make Single User' for them and their obdata.

See e.g. file below: make_single_user_for_linked_id.blend

Currently `Make Single User` operation (from the `Object -> Relations` 3DView menu e.g.) explicitly ignore any linked ID. From code history this seems to have been the behavior since a very long time (earliest commit I could find is from 2012 by @ideasman42 , but it's only a cleanup one...). @brecht, @ideasman42, do you guys know why this is the current behavior? ----------- This was reported as an issue by @JulienKaspar in this usecase: * Having several local objects using a same linked obdata. * If you want to get local single users duplicates of those obdata for some of those objects, you currently have to manually click on the 'user number' button in object data properties ID template for each of the objects. * Ideally you should be able to select desired objects in the 3DView, and just run 'Make Single User' for them and their obdata. See e.g. file below: [make_single_user_for_linked_id.blend](https://archive.blender.org/developer/F10413329/make_single_user_for_linked_id.blend)
Author
Owner

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

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

Added subscribers: @JulienKaspar, @ideasman42, @brecht, @mont29

Added subscribers: @JulienKaspar, @ideasman42, @brecht, @mont29

Not sure if I understand this correctly (is a linked-ID library-linked or a linked-duplicate ?), from checking behavior I think this is working properly/as-intended.

Making library-data local just means the library-data is stored locally in the file (which may still be shared between many objects).

Making single user shouldn't need to be done individually using the "single user" button as there is a menu for this "Object -> Relations -> Make Singe User".

Not sure if I understand this correctly (is a linked-ID `library-linked` or a `linked-duplicate` ?), from checking behavior I think this is working properly/as-intended. Making library-data local just means the library-data is stored locally in the file (which may still be shared between many objects). Making single user shouldn't need to be done individually using the "single user" button as there is a menu for this "Object -> Relations -> Make Singe User".
Author
Owner

Eeeeeh, must have been very tired or confused when I wrote that task... I meant 'Make Single User ignore linked IDs'! Will update task description.

Eeeeeh, must have been very tired or confused when I wrote that task... I meant 'Make Single User ignore linked IDs'! Will update task description.
Bastien Montagne changed title from Make Local operation ignores linked data-blocks. to Make Single User operation ignores linked data-blocks. 2021-10-21 12:31:36 +02:00

Ah, in that case I don't think there is a good reason for the current behavior, making single user can also make local.

Although exact behavior needs some thought.

For example, if two objects share a linked mesh - is it reasonable that one of the objects meshes remains linked and the other becomes local (because it's duplicated). While "correct" this could be confusing behavior.

Suggest that data which is made single user is also made local.


If there happens to be a use-case for skipping linked data entirely - that could be added as an option (although I doubt it's needed).

Ah, in that case I don't think there is a good reason for the current behavior, making single user can also make local. Although exact behavior needs some thought. For example, if two objects share a linked mesh - is it reasonable that one of the objects meshes remains linked and the other becomes local (because it's duplicated). While "correct" this could be confusing behavior. Suggest that data which is made single user is also made local. ---- If there happens to be a use-case for skipping linked data entirely - that could be added as an option (although I doubt it's needed).

In #91410#1239101, @ideasman42 wrote:
Ah, in that case I don't think there is a good reason for the current behavior, making single user can also make local.

Agreed.

> In #91410#1239101, @ideasman42 wrote: > Ah, in that case I don't think there is a good reason for the current behavior, making single user can also make local. Agreed.

This issue was referenced by c37121f16c

This issue was referenced by c37121f16c14519a9056217a2f02fc9078b6e05e
Author
Owner

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Bastien Montagne self-assigned this 2021-10-22 10:27:00 +02: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
4 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#91410
No description provided.