After separate: 2 curves, 1 action #36999
Labels
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#36999
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
%%%--- Operating System ---
Linux Mint 13 64-bit
2.68.0 r58536
2.68.5 r60361
When animating curves' Bevel Factor, after a "separate" operation, the resulting curves have both the same action and it cannot be unlinked.
Using the outliner is possible to see both objects have the same action under its object data (the action is not relative to the object, but to its data).
There is no way to unlink that action, or change it without affecting the other curve.%%%
Changed status to: 'Open'
%%%P.S.: there is one way to unlink it, by right-click on the animation data in the outliner and selecting "unlink".%%%
%%%I would have expected the Action data block to show up in the action editor. This works fine for objects, there you get a "2" button indicating the 2 users after separating mesh data into a second object which then shares the action, and you can make it unique or unlink. But for some reason the context update in Action editor only uses actual object data, not the animated curve data.
@JoshuaLeung: this happens in actedit_get_context:
Would it hurt to allow actions from other non-Object contexts in the editor? I think we need better ways to access anim data in non-object blocks.%%%
%%%This is currently a known limitation that's been on the todo for quite a while.
I'm not entirely against allowing the Action Editor to be used for assigning/editing actions attached to levels other than object. However, I also think that it's not a good idea to try and do anything "clever" like guessing which context a user wants to assign an action to, at least not without providing a clear indicator of what level they're currently editing, otherwise we get problems like users thinking that they're assigning an action to one context when in fact they're assigning to another.
There are really 2 parts to addressing the problem here:
Added subscriber: @KevinMackay
Added subscriber: @Sergey
@JoshuaLeung, shall we consider this a bug? Otherwise i'll move it to TODO.
Changed status from 'Open' to: 'Archived'
Added subscriber: @JulianEisel
Added note in the Todo list for now.