To make optional use of new alignment style - make an option to revert to old alignment #41680

Closed
opened 2014-09-01 18:15:36 +02:00 by Svyat · 9 comments

I totally disagree with idea of new number alignment in 2.7x. I personally find new data representation method uncomfortable and distracting. Since years and years it used to be center alignment in blender and it worked just fine. New method violates rules of perception. When I look for numerical information in a tab now I have to first of all to look at the left to find out what is it - for example it "x" next I have to move my eye to the right to get a number. When all data is centered eye got all information at first glance. Now glancing through for example "N" tab , at major visual place (optic center of a field) that is a center, I got a empty space! That is wrong - and that is not human friendly and ergonomically. I even do not mention issue with long tabs itself and manual data entry problem when cursor jumps to the left for data entry and then jumps back to right. I insist that is not ergonomically, please refer to studies of psychology of human perception. I do propose to make an option to turn on old alignment for people who find old alignment comfortable and useful.

Cheers

 
I totally disagree with idea of new number alignment in 2.7x. I personally find new data representation method uncomfortable and distracting. Since years and years it used to be center alignment in blender and it worked just fine. New method violates rules of perception. When I look for numerical information in a tab now I have to first of all to look at the left to find out what is it - for example it "x" next I have to move my eye to the right to get a number. When all data is centered eye got all information at first glance. Now glancing through for example "N" tab , at major visual place (optic center of a field) that is a center, I got a empty space! That is wrong - and that is not human friendly and ergonomically. I even do not mention issue with long tabs itself and manual data entry problem when cursor jumps to the left for data entry and then jumps back to right. I insist that is not ergonomically, please refer to studies of psychology of human perception. I do propose to make an option to turn on old alignment for people who find old alignment comfortable and useful. Cheers ```
Author

Changed status to: 'Open'

Changed status to: 'Open'
Campbell Barton was assigned by Svyat 2014-09-01 18:15:36 +02:00
Author

Added subscribers: @billrey, @ThomasDinges, @JoshuaLeung, @ideasman42, @brecht, @JonathanWilliamson, @xrg, @BassamKurdali, @jensverwiebe, @AditiaA.Pratama, @macouno-3

Added subscribers: @billrey, @ThomasDinges, @JoshuaLeung, @ideasman42, @brecht, @JonathanWilliamson, @xrg, @BassamKurdali, @jensverwiebe, @AditiaA.Pratama, @macouno-3

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

Added subscriber: @mont29

Added subscriber: @mont29

I) This is not a bug, but a feature request
II) It’s not up to you to set priority of a report
III) It’s not up to you to assign a report

For such topics, you can use IRC (for live discussion), ML lik bf-funboard, and forums. Not the tracker.

I) This is not a bug, but a feature request II) It’s not up to you to set priority of a report III) It’s not up to you to assign a report For such topics, you can use IRC (for live discussion), ML lik bf-funboard, and forums. Not the tracker.
Author

Added subscriber: @svt

Added subscriber: @svt
Author

If it's not up to me why there is such option as priority and possibility to assign report you are having fun of me mont29 ?

If it's not up to me why there is such option as priority and possibility to assign report you are having fun of me mont29 ?

https://developer.blender.org/project/view/12/

"These design tasks can only be created by developers that will implement a change, and by the Core UI team members listed below"

https://developer.blender.org/project/view/12/ "These design tasks can only be created by developers that will implement a change, and by the Core UI team members listed below"
Author

Never thought that there is such bureaucracy and chaos on blender developer site

Never thought that there is such bureaucracy and chaos on blender developer site
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#41680
No description provided.