VSE: Standardize reset retiming operator #123973

Merged
Richard Antalik merged 4 commits from eliphaz/blender:vse-improve-reset-retiming into blender-v4.2-release 2024-07-01 23:13:04 +02:00

Every retiming operator works on selected items -- either just selected
retiming keys or retiming keys and selected strips. However, the reset
retiming operator only works on the active strip.

This patch standardizes the behavior so that reset works the same
way as the other retiming operators: All selected strips or strips
associated with selected retiming keys have their retiming reset.
This gives more control to the user to reset many strips' retiming in bulk.

Every retiming operator works on selected items -- either just selected retiming keys or retiming keys and selected strips. However, the reset retiming operator only works on the active strip. This patch standardizes the behavior so that reset works the same way as the other retiming operators: All selected strips or strips associated with selected retiming keys have their retiming reset. This gives more control to the user to reset many strips' retiming in bulk.
John Kiril Swenson added 1 commit 2024-07-01 02:41:00 +02:00
Every retiming operator works on selected items -- either just selected
retiming keys or retiming keys and selected strips. However, the reset
retiming operator only works on the active strip.

This patch standardizes the behavior so that reset retiming works the
same way as the other retiming operators. This gives more control to the
user to reset many strips' retiming in bulk.
John Kiril Swenson requested review from Richard Antalik 2024-07-01 02:41:21 +02:00
John Kiril Swenson requested review from Aras Pranckevicius 2024-07-01 02:43:54 +02:00
John Kiril Swenson added 1 commit 2024-07-01 03:07:05 +02:00
John Kiril Swenson added 1 commit 2024-07-01 04:20:59 +02:00
Richard Antalik requested changes 2024-07-01 20:19:04 +02:00
Dismissed
Richard Antalik left a comment
Member

The reset retiming operator is not supposed to run when "retiming mode" (some key is selected) is active.

I would make this run purely on normal selection. IMO key selection is bad and error prone proxy to strip selection. Also not sure if this would be beneficial for any workflow.

The reset retiming operator is not supposed to run when "retiming mode" (some key is selected) is active. I would make this run purely on normal selection. IMO key selection is bad and error prone proxy to strip selection. Also not sure if this would be beneficial for any workflow.
John Kiril Swenson added 1 commit 2024-07-01 22:10:22 +02:00
Author
Member

The reset retiming operator is not supposed to run when "retiming mode" (some key is selected) is active.

I would make this run purely on normal selection. IMO key selection is bad and error prone proxy to strip selection. Also not sure if this would be beneficial for any workflow.

True, I've made the changes.

It may not make much of a difference but by standardizing the behavior hopefully it can be a little less confusing to new users, and give the ability to reset two+ strips at once without much headache. When trying out this operator for the first time I couldn't quite figure out which strips it was targeting since the behavior was different than other retiming ops.

> The reset retiming operator is not supposed to run when "retiming mode" (some key is selected) is active. > > I would make this run purely on normal selection. IMO key selection is bad and error prone proxy to strip selection. Also not sure if this would be beneficial for any workflow. True, I've made the changes. It may not make much of a difference but by standardizing the behavior hopefully it can be a little less confusing to new users, and give the ability to reset two+ strips at once without much headache. When trying out this operator for the first time I couldn't quite figure out which strips it was targeting since the behavior was different than other retiming ops.
Richard Antalik approved these changes 2024-07-01 22:27:58 +02:00
Richard Antalik merged commit 607445da5f into blender-v4.2-release 2024-07-01 23:13:04 +02:00
John Kiril Swenson deleted branch vse-improve-reset-retiming 2024-07-02 00:58:10 +02:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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
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#123973
No description provided.