Inconsistent text alignment for operator buttons #50438

Closed
opened 2017-01-16 00:54:04 +01:00 by Vilem Duha · 10 comments
Member

To put it simple, current state is:

Toolbar operator butons:

  • align left, if they have no icon
  • align to center, if they have icon

All other areas:

  • align to center, no metter if they have or haven't icon.
  • if icon is present, the alignment is offset to right from the buttons that don't have icons. If these are above/below, things get out of alignment

rest of the UI aligns everything to left in most cases.

possible solution 1 :
Align to left
if an icon is present in a column of buttons under each other, offset by icon width, also for buttons which don't have an icon.

this is consistent with menu drawing in 2.78, where icons aren't everywhere too.

possible solution 2
align left
drop icons for operator buttons completely. It is a question if these are actually of any use except for add primitive panel, where they are used a lot. Icons in operator buttons are actually so rare they often look like a mistake, or taking an operator out of context.

To put it simple, current state is: Toolbar operator butons: - align left, if they have no icon - align to center, if they have icon All other areas: - align to center, no metter if they have or haven't icon. - if icon is present, the alignment is offset to right from the buttons that don't have icons. If these are above/below, things get out of alignment rest of the UI aligns everything to left in most cases. possible solution 1 : Align to left if an icon is present in a column of buttons under each other, offset by icon width, also for buttons which don't have an icon. this is consistent with menu drawing in 2.78, where icons aren't everywhere too. possible solution 2 align left drop icons for operator buttons completely. It is a question if these are actually of any use except for add primitive panel, where they are used a lot. Icons in operator buttons are actually so rare they often look like a mistake, or taking an operator out of context.
Julian Eisel was assigned by Vilem Duha 2017-01-16 00:54:04 +01:00
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

Added subscriber: @VilemDuha

Added subscriber: @VilemDuha
Member

Added subscriber: @JoshuaLeung

Added subscriber: @JoshuaLeung
Member

This task is mainly about why buttons in toolbars may align text differently than buttons anywhere else in Blender. I don't see why this should be the case. Also reported in #41592.

There is an explicit check for toolbars in code to align text in operator buttons to the left if they don't have an icon. Added in c6dbbde16b. @JoshuaLeung, do you remember the reason for this?

Changing this would be a minor task, but would prefer to have approval from others first - also from the rest of the UI team.

(Note that I approved this design task.)

This task is mainly about why buttons in toolbars may align text differently than buttons anywhere else in Blender. I don't see why this should be the case. Also reported in #41592. There is an explicit check for toolbars in code to align text in operator buttons to the left if they don't have an icon. Added in c6dbbde16b. @JoshuaLeung, do you remember the reason for this? Changing this would be a minor task, but would prefer to have approval from others first - also from the rest of the UI team. *(Note that I approved this design task.)*
Member

Added subscriber: @Blendify

Added subscriber: @Blendify
Member

Poke.

Poke.

Added subscriber: @FilipMond

Added subscriber: @FilipMond

Seems like I can join with this proposal . . . That comes from practicle reason, if you try to eliminate borders of buttons to make them less prominent you loose visual connection between elements. In this example easily solved by moving text to left.

0f28a3fcf912f80555638a84fa38ec749af5952e.gif

Drop down icon with triangle in a corner is already used for tool bar icons. There it's separate action icon and corner, I mention that for visual continuity. Corner symbol in this size doesnt colide with icon square itself.

22e2cafbed5afa38c098a7abdaeabda707b3450a (1).gif

To see what elements are able to hold together without framing I set theme called Empty. Framing elements should be additional visual support not primary solution to distinguish buttons.
https://blenderartists.org/t/monoicons/1103103/59

Seems like I can join with this proposal . . . That comes from practicle reason, if you try to eliminate borders of buttons to make them less prominent you loose visual connection between elements. In this example easily solved by moving text to left. ![0f28a3fcf912f80555638a84fa38ec749af5952e.gif](https://archive.blender.org/developer/F3931627/0f28a3fcf912f80555638a84fa38ec749af5952e.gif) Drop down icon with triangle in a corner is already used for tool bar icons. There it's separate action icon and corner, I mention that for visual continuity. Corner symbol in this size doesnt colide with icon square itself. ![22e2cafbed5afa38c098a7abdaeabda707b3450a (1).gif](https://archive.blender.org/developer/F3931690/22e2cafbed5afa38c098a7abdaeabda707b3450a__1_.gif) To see what elements are able to hold together without framing I set theme called Empty. Framing elements should be additional visual support not primary solution to distinguish buttons. https://blenderartists.org/t/monoicons/1103103/59
Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Member

I removed the special handling of toolbar buttons a bit ago (6e8a76c96a), so operator items should align consistently by default now. Closing this.

@FilipMond this is something that should be handled by the theme. Ideally they'd be able to set the text alignment (e.g. like CSS does it). However making such general design decisions just for these unusual theme usages is not something we should do.

I removed the special handling of toolbar buttons a bit ago (6e8a76c96a), so operator items should align consistently by default now. Closing this. @FilipMond this is something that should be handled by the theme. Ideally they'd be able to set the text alignment (e.g. like CSS does it). However making such general design decisions just for these unusual theme usages is not something we should do.
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
4 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#50438
No description provided.