UI: Consistent Use of Chevron Disclosure Icons #116240
No reviewers
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
9 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#116240
Loading…
Reference in New Issue
No description provided.
Delete Branch "Harley/blender:Disclosures"
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?
For icons that represent collapsible and collapsed content we use a
variety of icons: chevrons and closed triangles of varying
proportions. This PR makes everything use a chevron for consistency.
A nice way to compare is by looking at this 2-frame animated GIF full screen:
I like the consistency, but as someone who works with hierarchies a lot, I find the arrow to be a nice, bold, very visible indent indicator. If this chevron is a text character, can we please try turning it bold ? It doesn't affect the spreadsheet so much imo because there's never more than one hierarchy level.
It isn't a text character, but is an icon.
But it would helpful to take the image linked above (just the layer with the chevrons) into an image editor and play around with it until you have a size and width and boldness you like. You might be happy with something slightly smaller but with slightly thicker features, so some other combination. And then we could consider changing the icons.
I prefer the filled triangle to the chevron in places such as the outliner and the timeline, as it is graphically more dominate in a place where many characters of text and other various grid lines are also present.
You prefer if we used the filled triangle for all show/hide uses, or prefer a mix?
The mix doesn't bother me too much, honestly - but, I can see why it would catch your attention. I think I've just gotten used to UI inconsistency in Blender (for better or worse.)
But of a goal with "ok, let's try and be consistent" - if I were to pick a single one, I would prefer the filled triangle. Blender is quite text-heavy with rows of text labels in a lot of ways, and the Chevron is... well, just more text. I think Filled breaks it up a bit, and visually presents as "UI element" vs "text label'.
It is always an option to use a filled triangle for all these show/hide uses, as long as we pick one. And then use the chevron for the other uses. Or use one for everything. I just hate having three types that we use in such an inconsistent manner.
I think filled triangles look better for almost everything, as it was pointed out it catches eye more and distinguishes from text. But chevrons look much better for panels, it would be shame to lose one.
So I propose this logic:
Use chevron when expanding panels. Chevron becomes a symbol of "properties under here", it indicates to user that something, panel, box, or whatever has more properties
Use filled triangle when expanding children/hierarchy. That becomes symbol of "children under here". So in dope sheet channels, tree view, outliner, where text is dominant we dont lose that symbol.
I think this makes sense and communicates icons well enough.
I would choose consistent filled triangles everywhere, rather than consistent chevrons.
Triangles are easy to spot, not looking like a font element, more self explanatory, standard in many other softwares.
Yes, that is certainly a possibility too.
I also lean towards the filled in triangle and, if we want to keep both, also would use chevrons only for panels. To me, rather than the mix of chevron and triangle, is much more irritating the slight difference between the triangle in the outliner and the "fatter" one in the Spreadsheet/asset browser/animation editors.
Chevron for panels and menus is ok. Everywhere else where you can see direct parent child relationship, I would prefer triangles.
Of if we can choose only one, I would lean towards triangle everywhere.
Approving this as agreed during the latest module meeting.
As it improves consistency and readability. To be combined with #117654
It looks like something went wrong merging main into
node_templates.cc
.@ -997,9 +991,6 @@ static void ui_node_draw_input(uiLayout &layout,
split_wrapper.decorate_column, &inputptr, "default_value", RNA_NO_INDEX);
break;
}
case SOCK_MENU:
Merge error.
@ -396,4 +395,1 @@
}
else if (dynamic_cast<const decl::Menu *>(&socket_decl)) {
item.socket_type = SOCK_MENU;
}
Merge error.
@ -24,3 +24,3 @@
#include "BKE_context.hh"
#include "BKE_lib_id.hh"
#include "BKE_lib_id.h"
Merge error.
@ -943,3 +937,3 @@
if (dependency_loop) {
uiItemL(row, RPT_("Dependency Loop"), ICON_ERROR);
uiItemL(row, IFACE_("Dependency Loop"), ICON_ERROR);
Merge error.
@brecht - It should work now
The diff still shows unrelated changes.
Yeah, that was weird. Not sure how those changes were hallucinated.
I think that is quite strange that the chevrons were approved and merged when almost all the comments in this pull request stated they preferred filled triangles ?