UI: Label design pattern causes confusion #95604
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#95604
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?
In the alembic export settings, for example, an option appears to be labeled with the text in reverse order compared to its name in the tooltips.
This pattern is meant to reduce clutter by not repeating identical parts of adjacent labels and relying on the user to infer the meaning. Perhaps there is a better way to communicate this without repeating the text.
See the example below:
"Transform Samples" appears to be called "Samples Transform".
"Geometry Samples" appears to be called "Geometry"
However, the UI is meant to be interpreted as follows...
The same pattern is used for Frame start/end (also displayed in the image above.) In this case, the intent is more clear in part due to the connected button sliders, and also, start frame and end frame are familiar concepts that any user would expect to find next to each other.
Transform samples and geometry samples are more abstract concepts by comparison.
To reproduce
Added subscriber: @tiles
Added subscriber: @PratikPB2123
Changed status from 'Needs Triage' to: 'Confirmed'
Thanks for the report. Can be improved to maintain consistency.
Related https://developer.blender.org/T91541
@PratikPB2123 I have uploaded a diff here D14469: Fix #95604: Naming inconsistencies in alembic exporter options, please review.
Added subscribers: @HooglyBoogly, @Ujwal-Kundur, @Ethan-Hall
Perhaps a design tweak could be discussed to help prevent confusion. However, I am removing this from #good_first_issue.
Alembic exporter - name inconsistencies in the optionsto UI: Label design pattern causes confusionIn this this case the two "samples" buttons should be aligned so it's clear that they should be interpreted as a group.
@HooglyBoogly I still wish it looked a bit more elegant. How do you feel about something like this?
Split Label Proposal
{F13022822 size=full}
This design allows for splitting a label with a visual indicator to help clarify that the leading part of the label applies to both items (even if the buttons are not (or cannot be) aligned/connected)
@Ethan-Hall Looks great! How about a drop-down for the buttons which are context dependent? It would reduce visibility for a few of the options, but allows grouping attribute related buttons together.
It's an interesting idea, but personally I would rather not increase the complexity in this area, both visually and in the code. I think it looks a bit busy honestly, the alignment is a fair amount more arbitrary after with that line IMO.
I think using alignment to signify this connection more consistently would be helpful though.