Anim: Add "Add/delete" track operations to NLA context menu #114202
No reviewers
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#114202
Loading…
Reference in New Issue
No description provided.
Delete Branch "nrupsis/blender:NLA-context-menu"
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?
Updating NLA context menu, adding in more relevant track operations (tracks add, tracks add above, tracks delete).
Old (4.0)
New (4.1)
Anim: Update NLA "Channel Context Menu" to be "NLA Tracks" with some more optionsto Anim: Update NLA "Channel Context Menu" to be "NLA Tracks" + add/delete operationsAnim: Update NLA "Channel Context Menu" to be "NLA Tracks" + add/delete operationsto WIP: Anim: Update NLA "Channel Context Menu" to be "NLA Tracks" + add/delete operationsWIP: Anim: Update NLA "Channel Context Menu" to be "NLA Tracks" + add/delete operationsto Anim: Update NLA "Channel Context Menu" to "NLA Tracks" + add/delete operationsSuggestion: "Remove Empty Animation Data" -> "Remove Empty" ?
The user is already in the context of Tracks, and that's really what they're cleaning up.
Hey, I'm all for changing the terminology of NLA "Channel" to "Track" if that is what you guys want. But...
It could get a bit more involved to make this change completely. There are a few other client-facing uses of "Channel", like in operator names, in some error messages, etc. There is a keymap name of "NLA Channels" that contains "channel" items, including one that calls this context menu:
So again, no problem about changing it, but I just wanted to make sure you know you could be chasing down inconsistencies for a while.
I personally think we should change it across the board. I'm 98% confident the Animation & Rigging module will agree, but I'll run it by them again.
I'm also happy to do the work. I can either update this PR or create follow up(s), whatever your preference is.
Anim: Update NLA "Channel Context Menu" to "NLA Tracks" + add/delete operationsto Anim: Add "Add/delete" track operations to NLA context menu@Harley Updating this PR to just be adding in new Track operators to the context menu. NLA channels rename has been moved to new PR
That makes sense.
Ultimately these context menu items should be how you guys prefer it, so take any advice from me with very light weight.
I would consider expanding the description of the regular
nla.tracks_add
item so that both items are equally explicit on where the new track is positioned. Otherwise you have to make assumptions about the first item based on the name of the second one. "Add Tracks Below Selected" & "Add Tracks Above Selected" perhaps. That might make you think about what order they should be in.If you do so you might find that the pair look a little awkward, both having such similar names. But add a separator after them and they would then look like a nice logical pair and the "add" items would have a separation from "delete" to help avoid accidents.
in terms of functionality this is a clear yes
I agree with harley that it's probably better to be explicit in the label. If there is an "...above selected" there should be a "...below selected"
but giving my approval since I don't feel super strongly about that
Tested it out. I like the direction a lot.
I think
Add Tracks...
->Add Track ...
would be better. It only adds a single track.Also, at the moment both
Add Tracks Above Selected
andAdd Tracks Below Selected
add a track above the selected track, at least in my testing.@nathanvegdahl ah, I guess the opposite of
above_selected = True
is not to add tracks below selected, rather just add em to the top of the stack...If people think adding in "Add tracks below selected" option to the operator (and menu), I can add that as a follow up change.
@nrupsis Ah, got it. Yeah, I think if there's an "add above" there should probably be an "add below". But agree that's better as follow up PR.
Looks good to me!