UI: Improvements to Confirmation of Apply Modifier #117156

Merged
Harley Acheson merged 12 commits from Harley/blender:ConfirmApplyModifier into main 2024-02-24 01:38:42 +01:00
Member

A more informative confirmation dialog to confirm that the user wishes
to apply modifier to an object with multiple users.


Current

image

Proposed

image

A more informative confirmation dialog to confirm that the user wishes to apply modifier to an object **with multiple users**. --- Current ![image](/attachments/a58f4934-f41b-455f-a40d-6f2a86e5ea9e) Proposed ![image](/attachments/c3a99aa8-f8dd-49e7-95a5-b78c250d5275)
Harley Acheson added 1 commit 2024-01-16 03:11:27 +01:00
6f9577bdfe UI: Improvements to Confirmation of Apply Modifier
A more informative confirmation dialog to confirm that the user wishes
to apply modifier to an object with multiple users.
Harley Acheson added this to the User Interface project 2024-01-16 03:11:53 +01:00
Harley Acheson requested review from Pablo Vazquez 2024-01-16 03:12:05 +01:00
First-time contributor

Just a quick note, right now these two statements (the dialog title, and the dialog message) contain 3 items, 1 of which ("Apply modifier") is common to both sentences, but in a reversed order. This muddies a bit the conveyed meaning and the order of operations (=1.data is made single-user, 2.modifier is applied, and 3.modifier is removed)

Since the modifier being removed is a consequence of applying it, I would change the tooltip in object.modifier_apply() to solely "Apply modifier". I assume the additional information was initially added there because the old dialog infrastructure didn't allow for extended descriptions, so perhaps move the mention of the modifier being removed inside this new description (the one from this commit) : "Make data single-user, apply modifier and remove it from the stack".

Finally, I would change "modifier stack" to "modifier list" because stack suggests a bottom-to-top order -like 2D layers-, whereas modifiers are evaluated top-to-bottom. I think there's a mixed usage in the interface, as I remember reading "modifier list" (not sure where exacty or how to search for it efficiently).

Just a quick note, right now these two statements (the dialog title, and the dialog message) contain 3 items, 1 of which ("Apply modifier") is common to both sentences, but in a reversed order. This muddies a bit the conveyed meaning and the order of operations (=1.data is made single-user, 2.modifier is applied, and 3.modifier is removed) Since the modifier being removed is a consequence of applying it, I would change the tooltip in object.modifier_apply() to solely "Apply modifier". I assume the additional information was initially added there because the old dialog infrastructure didn't allow for extended descriptions, so perhaps move the mention of the modifier being removed inside this new description (the one from this commit) : "Make data single-user, apply modifier and remove it from the stack". Finally, I would change "modifier stack" to "modifier list" because stack suggests a bottom-to-top order -like 2D layers-, whereas modifiers are evaluated top-to-bottom. I think there's a mixed usage in the interface, as I remember reading "modifier list" (not sure where exacty or how to search for it efficiently).
Harley Acheson added 2 commits 2024-01-16 20:29:59 +01:00
Author
Member

@HadrienBrissaud - I updated the PR and the screen captures in the first comment. Is this what you had in mind?

@HadrienBrissaud - I updated the PR and the screen captures in the first comment. Is this what you had in mind?
Contributor

As a small stylistic proposal, we could capitalize "Modifier" only in the dialog title to make it a bit more balanced, resulting in "Apply Modifier", making it closer in style to operator titles, as can be seen in the "Add Modifier" button.

As a small stylistic proposal, we could capitalize "Modifier" only in the dialog title to make it a bit more balanced, resulting in "Apply Modifier", making it closer in style to operator titles, as can be seen in the "Add Modifier" button.
First-time contributor

@HadrienBrissaud - I updated the PR and the screen captures in the first comment. Is this what you had in mind?

Yes, pretty much. I think we're gaining in clarity by separating the action from its side-effects.

> @HadrienBrissaud - I updated the PR and the screen captures in the first comment. Is this what you had in mind? Yes, pretty much. I think we're gaining in clarity by separating the action from its side-effects.
Harley Acheson added 2 commits 2024-01-17 02:46:51 +01:00
Harley Acheson added 2 commits 2024-01-25 20:40:44 +01:00
Harley Acheson added 2 commits 2024-01-29 20:35:13 +01:00
Harley Acheson added this to the 4.2 LTS milestone 2024-02-05 19:28:30 +01:00
Harley Acheson added 2 commits 2024-02-13 22:11:16 +01:00
Harley Acheson added 1 commit 2024-02-24 01:37:33 +01:00
Harley Acheson merged commit 5eda7c9fd3 into main 2024-02-24 01:38:42 +01:00
Harley Acheson deleted branch ConfirmApplyModifier 2024-02-24 01:38:45 +01:00
Sign in to join this conversation.
No reviewers
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
3 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#117156
No description provided.