General purpose cleanup tool #44772
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#44772
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?
We have a few areas where a cleanup tool can be helpful to keep a project organised:
One possible way to handle this is to add cleanup options to related operators. Like for example adding a "remove empty vgroups" option to the vertex clean tool.
Another possible way is to create a cleanup operator that can take a bunch of options (settings).
Such a tool could be directly built into Blender, or it could be created as an Addon.
If you know more areas where a cleanup tool would be helpful, then please add your finds to the list. Or if you have ideas how such a tool should operate, please add your ideas to this task.
Changed status to: 'Open'
Added subscribers: @GaiaClary, @ideasman42
Added subscriber: @mont29
This is a bit of a fuzzy area… Orphaned datablocks are already visible and deletable in outliner iirc.
Think this is needed, and also part of a larger project related to import/export (including 3DPrinting tools we already have, thinks like mesh.validate that are not directly exposed to user, and common needs that could be nice to have for export, like orientation changes baking, etc.).
Personally, I would rather aim at a single place where we handle that (probably an addon), which would define UI (implementation can then reuse existing C code, implement new needed one in py or C depending on performance needs, etc.). Our operators already tend to do too much things…
But there are many ways to see that imho, our UI team may be interested on that topic too, how to present a bunch of tools with common purpose but touching many different parts of Blender.
Could be something for the outliner too?
Added subscriber: @sindra1961
It is different from the purpose of this thread, but wants to ask you a question.
Is it difficult to display a different layer every 3DView?
What is designed not to function individually though there is layer setting in all 3DView is mysterious.
Closing since this is more of a feature request and not specific enough to be actionable. Right click select is a better place for this sort of thing nowadays.