no UI for 'clear Object Motion paths' #31893

Closed
opened 2012-06-21 19:44:48 +02:00 by Dalai Felinto · 7 comments

%%%I can create, update but not remove an object motion path through the UI
(also, shouldn't it be Motion Path instead of Paths?)

thanks%%%

%%%I can create, update but not remove an object motion path through the UI (also, shouldn't it be Motion Path instead of Paths?) thanks%%%
Author
Owner

Changed status to: 'Open'

Changed status to: 'Open'
Member

%%%"Clear Paths" is actually available in the toolbar object tools - which will clear all selected paths.
Dont know the design decision behind this and looking at http://aligorith.blogspot.de/2012/05/motion-paths-gui-cleanup.html doesnt really mention this issue.
Would make sense to have a button in propertiy editor as well though it would have to work on active (vs. all selected) then, right?

"Motion Paths" vs. "Paths": no strong opinion on that (maybe that was just chosen to save some space?)%%%

%%%"Clear Paths" is actually available in the toolbar object tools - which will clear all selected paths. Dont know the design decision behind this and looking at http://aligorith.blogspot.de/2012/05/motion-paths-gui-cleanup.html doesnt really mention this issue. Would make sense to have a button in propertiy editor as well though it would have to work on active (vs. all selected) then, right? "Motion Paths" vs. "Paths": no strong opinion on that (maybe that was just chosen to save some space?)%%%

%%%Thomas, what our UI mafia would say on that?

Just note from me: i don't feel nice adding extra button to properties region, this sounds like duplicated functionality. I'd say it's more matter of making better documentation on this,%%%

%%%Thomas, what our UI mafia would say on that? Just note from me: i don't feel nice adding extra button to properties region, this sounds like duplicated functionality. I'd say it's more matter of making better documentation on this,%%%
Member

%%%OK, I've attached a patch with following changes (still think the bugreport has a point):

  • adds a button "Clear Paths" to the Property Editor
  • makes both operators "OBJECT_OT_paths_clear" and "OBJECT_OT_paths_update" functionality aware of where it was called from
  so when they are called from the Properties Editor they will only operate on the object in this context (and not on all selected)
  note: an object might also be pinned in the Property Editor and with this patch it is made sure that the op will operator on THIS pinned object
  (which doesnt even need to be selected)
  • (also a little change to the panels layout which admittetly "wastes" a little space but groups the settings what to show - this might be debatable...)
  • tooltip might need a better phrase
  • left the motion path ops relating to bones untouched (they are in the armature context - not a single bone - so should be fine like this?)
  • ... style is a little clumsy / some duplicated code (see comments in patch) ...%%%
%%%OK, I've attached a patch with following changes (still think the bugreport has a point): - adds a button "Clear Paths" to the Property Editor - makes both operators "OBJECT_OT_paths_clear" and "OBJECT_OT_paths_update" functionality aware of where it was called from ``` so when they are called from the Properties Editor they will only operate on the object in this context (and not on all selected) note: an object might also be pinned in the Property Editor and with this patch it is made sure that the op will operator on THIS pinned object (which doesnt even need to be selected) ``` - (also a little change to the panels layout which admittetly "wastes" a little space but groups the settings what to show - this might be debatable...) - tooltip might need a better phrase - left the motion path ops relating to bones untouched (they are in the armature context - not a single bone - so should be fine like this?) - ... style is a little clumsy / some duplicated code (see comments in patch) ...%%%
Member

%%%Fixed a duplicate of this bug. On second thought, it does make sense to have one of these buttons in the properties editor, since users seem to want to look there for this.%%%

%%%Fixed a duplicate of this bug. On second thought, it does make sense to have one of these buttons in the properties editor, since users seem to want to look there for this.%%%
Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

%%%This has been fixed in SVN 51036.%%%

%%%This has been fixed in SVN 51036.%%%
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
5 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#31893
No description provided.