"Lock" with node group asset "Append & Reuse" to prevent accidental editing #114058

Open
opened 2023-10-23 12:17:13 +02:00 by Hans Goudey · 2 comments
Member

For the essentials asset bundle and other bundles that use "Append & Reuse" currently it's possible to edit the appended node groups, which will affect every new use.

The best way to make this more intuitive would be locking the appended node groups at the UI level. We would either require duplicating the data-block to edit the data or explicitly clearing the lock.

For the essentials asset bundle and other bundles that use "Append & Reuse" currently it's possible to edit the appended node groups, which will affect every new use. The best way to make this more intuitive would be locking the appended node groups at the UI level. We would either require duplicating the data-block to edit the data or explicitly clearing the lock.
Hans Goudey added the
Type
To Do
label 2023-10-23 12:17:13 +02:00
Hans Goudey added this to the Nodes & Physics project 2023-10-23 12:17:15 +02:00
Author
Member

The specific UI design still needs to be figured out, but hopefully it would just involve similar checks to the existing ones for linked node groups. The "lock" would probably be a node group property, though it might be worth considering making it for all data-blocks, not just node groups.

The specific UI design still needs to be figured out, but hopefully it would just involve similar checks to the existing ones for linked node groups. The "lock" would probably be a node group property, though it might be worth considering making it for all data-blocks, not just node groups.
Member
  • There should be an explicit unlocking process to enable replacing all users at once.
  • There should be no way to re-lock.
  • This can be stored on the ID (as opposed to the node group) so it can be used elsewhere in the future

(From talking about this with Hans in person)

- There should be an explicit unlocking process to enable replacing all users at once. - There should be no way to re-lock. - This can be stored on the `ID` (as opposed to the node group) so it can be used elsewhere in the future (From talking about this with Hans in person)
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 Assignees
2 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#114058
No description provided.