UI: Improvements to Confirmation of Apply Transforms #117157

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

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


Current

image

Proposed

image

A more informative confirmation dialog to confirm that the user wishes to apply transforms to an object with multiple users. --- Current ![image](/attachments/8dada088-8fe4-4ccd-a46d-69d9d461c392) Proposed ![image](/attachments/7b72e420-f288-45cf-bfe1-d71106c81452)
Harley Acheson added 1 commit 2024-01-16 03:19:01 +01:00
a76181c191 UI: Improvements to Confirmation of Apply Transforms
A more informative confirmation dialog to confirm that the user wishes
to apply transforms to an object with multiple users.
Harley Acheson added this to the User Interface project 2024-01-16 03:19:17 +01:00
Harley Acheson requested review from Pablo Vazquez 2024-01-16 03:19:38 +01:00
First-time contributor

While this PR does not create the following problem, it does repeat an existing problem - the error message itself is rather misleading and confusing.

Specifically, "Create new object-data users..."

If I hit Cntl A, to apply Scale on a cube with several instanced copies - how exactly is this creating "new users"? New users implies "some additional new cubes are going to be created." This is obviously not what happens.

While this PR does not create the following problem, it does repeat an existing problem - the error message *itself* is rather misleading and confusing. Specifically, **"Create new object-data users..."** If I hit Cntl A, to apply Scale on a cube with several instanced copies - how exactly is this creating "new users"? New users implies "some additional new cubes are going to be created." This is obviously not what happens.

It will duplicate mesh and curve datablocks, which is what "object-data users" is referring to.

Maybe more clear wording would be: "Duplicate geometry data-blocks and apply transformations"

It will duplicate mesh and curve datablocks, which is what "object-data users" is referring to. Maybe more clear wording would be: "Duplicate geometry data-blocks and apply transformations"
Harley Acheson added 2 commits 2024-01-17 20:10:22 +01:00
Author
Member

I simplified the title slightly to "Apply Object Transformations" and the message to Brecht's suggested "Duplicate geometry data-blocks and apply transformations". Updated the captures in the first comment.

I simplified the title slightly to "Apply Object Transformations" and the message to Brecht's suggested "Duplicate geometry data-blocks and apply transformations". Updated the captures in the first comment.

Sorry, looking at this again I think we could explain it a little better:
"Duplicate geometry data-blocks with multiple users and apply transformations"

Sorry, looking at this again I think we could explain it a little better: "Duplicate geometry data-blocks with multiple users and apply transformations"
Harley Acheson added 1 commit 2024-01-17 20:19:25 +01:00
Author
Member

Updated message to "Duplicate geometry data-blocks with multiple users and apply transformations". Capture in first comment updated.

Updated message to "Duplicate geometry data-blocks with multiple users and apply transformations". Capture in first comment updated.
First-time contributor

Perhaps something less... I don't know... rigidly code-speak?

"apply transformations to all objects sharing this data"

Perhaps something less... I don't know... rigidly code-speak? "apply transformations to all objects sharing this data"
Author
Member

Perhaps..."apply transformations to all objects sharing this data"

I do like the friendlier "sharing this data". But the "this" might be unclear, "all objects" could be misunderstood, and I think it misses the bit where shared data gets duplicated.

We could use two message lines:

"Warning: Multiple objects share the same data."
"Make single user and then apply transformations?"

> Perhaps..."apply transformations to all objects sharing this data" I do like the friendlier "sharing this data". But the "this" might be unclear, "all objects" could be misunderstood, and I think it misses the bit where shared data gets duplicated. We could use two message lines: "Warning: Multiple objects share the same data." "Make single user and then apply transformations?"

I think the two lines help.

An alternative for the second line could be "Duplicate geometry data before applying transformations?"

But either works.

I think the two lines help. An alternative for the second line could be "Duplicate geometry data before applying transformations?" But either works.
First-time contributor

We could use two message lines:

"Warning: Multiple objects share the same data."
"Make single user and then apply transformations?"

I like that, as it doesn't make the artist have to think about what a word means.

(Sometimes blender uses words in unique ways, that blur the intended comprehension)

> We could use two message lines: > > "Warning: Multiple objects share the same data." > "Make single user and then apply transformations?" > I like that, as it doesn't make the artist have to think about what a word means. (Sometimes blender uses words in unique ways, that blur the intended comprehension)
Author
Member

One thing I'm trying to avoid are questions that beg for a "yes" or "no" answer. This can cause some hesitation where you have to work out exactly what you are answering yes or no to, and this gets a bit harder for people using a language that is not their first. By putting verbs on the buttons, like "Delete" or "Apply", or "Save" it removes that possible confusion.

One thing I'm _trying_ to avoid are questions that beg for a "yes" or "no" answer. This can cause some hesitation where you have to work out exactly what you are answering yes or no to, and this gets a bit harder for people using a language that is not their first. By putting verbs on the buttons, like "Delete" or "Apply", or "Save" it removes that possible confusion.
Harley Acheson added 1 commit 2024-01-18 00:38:30 +01:00
Harley Acheson added 2 commits 2024-01-25 20:46:26 +01:00
Harley Acheson added 2 commits 2024-01-29 20:49:01 +01:00
Brecht Van Lommel approved these changes 2024-01-30 15:54:56 +01:00
Harley Acheson added this to the 4.3 milestone 2024-02-05 19:28:35 +01:00
Harley Acheson modified the milestone from 4.3 to 4.2 LTS 2024-02-05 19:28:40 +01:00
Harley Acheson added 2 commits 2024-02-13 22:15:13 +01:00
Harley Acheson added 1 commit 2024-02-24 01:27:54 +01:00
Harley Acheson merged commit 2c8a3243ee into main 2024-02-24 01:33:01 +01:00
Harley Acheson deleted branch ConfirmApplyTransforms 2024-02-24 01:33:03 +01:00
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
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#117157
No description provided.