Expand: Menu operators need to be updated #104023
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#104023
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?
(NOTE) This task is part of the community & sub tasks of the workboard. Anyone is free to pick up this task and contribute. For any questions or needed reviewers, please tag @JosephEagar and @JulienKaspar.
The menu operators for Expand are currently using the wrong arguments and are out of sync with the keymap entries.
These should match so the shortcuts will also show up in the menus:
So the operators need to have these properties:
Expand Mask by Topology: Invert=False, Preserve Previous=True, Auto-Create=False
Expand Mask by Normals: Invert=False, Preserve Previous=True
Expand Face Set by Topology: Invert=False, Preserve Previous=False, Modify Active=False
Expand Active Face Set: Invert=False, Preserve Previous=False, Modify Active=True
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscribers: @JulienKaspar, @JosephEagar
Added subscriber: @Patrick-Foley
I'm looking into this as my first contribution.
From the review comments when these features were added, it seems the desired behavior for both tools is to start the mask black and flood it white, and this is their behavior currently.
Removing the
invert=False
parameter from "Expand Mask by Normals" lets it fall back on the same default, and has no effect. However, removinginvert=True
from "Expand Mask by Topology" predictably changes the tool's behavior, starting the mask white and flooding it black.I take it the desired result of the change should be that the tools continue to operate as before? If so, it seems that some adjustment of the lower-level implementation would be required. I'm not very familiar with the tool's implementation, so I'm not sure exactly where this more hard-coded inversion behavior (when expanding mask by topology) comes from, or the ramifications of changing it to be in line with expanding by normals.
[edit: when the "[...] by Topology" and "[...] by Normals" tools are sent the same
invert
value (in this caseinvert=False
), their mask-filling behavior is opposite to each other. I thought perhaps I could find a smoking gun for this deeper into the code, so I also checked the filter-cache'sinvert
value for both tools while they were running. But they're both the same! (in this case set tofalse
)]@Patrick-Foley
I'm sorry for the not being clear enough on the current state of the Expand operators.
@JosephEagar is current fixing some issues at the moment. I'd suggest to wait a bit until he made the needed fixes first.
But to clarify: The desired result is that when using these Mask Expand operators:
F
a white unmasked area will be expandedE
The operator to expand by Normals still needs a fix to not fill the mesh island and to have the inverted effect by default.
This task is specifically about making sure that the menu operators do not override the default behavior.
@Patrick-Foley The issues I mentioned are now resolved.
The best way to resolve this task properly is to match the menu operators with the same properties of the keymap entries. This way the shortcuts will also show up in the menus:
So the operators need to have these properties:
Expand Mask by Topology: Invert=False, Preserve Previous=True, Auto-Create=False
Expand Mask by Normals: Invert=False, Preserve Previous=True
Expand Face Set by Topology: Invert=False, Preserve Previous=False, Modify Active=False
Expand Active Face Set: Invert=False, Preserve Previous=False, Modify Active=True
I'll update the task description.
Mask Expand: Menu operators should not set invert stateto Expand: Menu operators need to be updatedAlright, diff file set up here:
https://developer.blender.org/D17191
Should make for a simple enough review.
@JulienKaspar
@Patrick-Foley Sorry that the review happened so close to the migration to the new site. Could you reupload the patch so we can finish the review?
@JulienKaspar
I'm having some troubles setting the new workflow up (can't seem to verify my public key), but if and when I get that sorted I'll be happy to get a push request in and link it here.
If you'd like me to literally upload the diff file here I can do that as well, just let me know.
@JulienKaspar
Alright, if I understand correctly, this is what you need?
82d9296b97
@Patrick-Foley That works great. If you can create a pull request we can accept the changes and have it merged.
Patrick Foley referenced this issue2023-02-10 13:27:10 +01:00
@JulienKaspar
Got it. Here it is!
#104568
Julien Kaspar referenced this issue2023-02-10 13:55:47 +01:00
@Patrick-Foley Thanks! I added the reviewers, the module as a tag and the issue hash in the title ;)