Multi-Object-Mode: Operators that need refactor on their logic #56948
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#56948
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?
Some operators are working for multiple-object editing however are still not fully benefiting from it.
The most common case is that the operator works but only if all the objects have the same transformation matrix.
MESH_OT_select_similar(SIMEDGE_FACE_ANGLE, SIMFACE_AREA, SIMFACE_PERIMETER).0c1934f3c2
MESH_OT_knife_project and MESH_OT_knife_tool.
Need to convert the code from screen space to world space. More details on D3637.
UV_OT_weld (UV_STRAIGHTEN, UV_STRAIGHTEN_X, UV_STRAIGHTEN_Y).
The current logic to determine the first and last selected vertex is not very compatible with multi-object. We should be able to select vertices from different objects, and use their position to determine the line extremes.
LATTICE_OT_flip
The axis need to be in world space, not local space.
CURVE_OT_select_similar(SIMCURHAND_DIRECTION).ab77f5b5fe
Need to calculate direction taking scale into consideration.
Added subscribers: @dfelinto, @Brentron, @semaphore, @rjrodd, @GNUton, @eoinoneill, @alourenco, @Scaredyfish, @ideasman42
Removed subscribers: @Scaredyfish, @alourenco, @eoinoneill, @GNUton, @rjrodd, @semaphore, @Brentron
Added subscriber: @zazizizou
Not sure if
LATTICE_OT_flip
should be really using a global axis instead of local one. If you have two objects for example, flipping on a global x-axis would effectively mean flipping each object on local axis, and then swap the position of the two objects.The image shows an example of two flipped lattices on the global axis. Note how the origins of the two objects have been swapped, since flipping happened in edit mode.
I think this is not desired, so
LATTICE_OT_flip
should probably be kept as it is. In case this behavior is desired, then it can be done in object mode, e.g. scale by -1.You are assuming the objects are not rotated, which is not always the case.
My point was that the objects might get translated in an undesired way, because flipping happens in edit mode.
So maybe at least give the user a choice? e.g. by taking into account the pivot point (median point or individual origins) as we did with snap selection to cursor?
Added subscriber: @PratikPB2123
Added subscriber: @HobbesOS
I have been working on multi-object edit mode support for the knife tool and knife project as part of my GSOC project .
After experimenting with knife project, it seems it already supports mult-object edit mode. You are able to use multiple objects for projection like so (click in for gif):
I don't believe it would be possible to differentiate between objects used for projection and objects being projected onto. Therefore, I would consider it to work fully as expected in multi-object edit mode.