Consistent and improved modal operator status display #56599

Open
opened 2018-08-29 11:49:45 +02:00 by Brecht Van Lommel · 10 comments

We need to go through all usage of ED_workspace_status_text and ED_area_status_text and make it use the new convention:

  • The statusbar shows keymaps, with the new keymap drawing with icons.
  • Area header shows values and state being edited, so it's close to where the user is looking.

Some example issues:

  • Knife shows mixed keymap and state text in the status bar, should be split up.
  • Transform operator shows a long list of keymap items, could be organized to show fewer.
We need to go through all usage of `ED_workspace_status_text` and `ED_area_status_text` and make it use the new convention: * The statusbar shows keymaps, with the new keymap drawing with icons. * Area header shows values and state being edited, so it's close to where the user is looking. Some example issues: * Knife shows mixed keymap and state text in the status bar, should be split up. * Transform operator shows a long list of keymap items, could be organized to show fewer.
Author
Owner

Added subscriber: @brecht

Added subscriber: @brecht

#69638 was marked as duplicate of this issue

#69638 was marked as duplicate of this issue

#56600 was marked as duplicate of this issue

#56600 was marked as duplicate of this issue
Brecht Van Lommel changed title from Finish keymap display in status bar to Improve keymap display in status bar 2018-08-29 14:40:03 +02:00
Member
Added subscribers: @AlbertoVelazquez, @jenkm, @Blendify, @lichtwerk, @WilliamReynish

I think this idea is a mistake. All information must appear in the header area. You can't separate the parameter from the shorcut needed to change it and you have to be passing from one bar to another to know which hotkey is the one you have to press.

Even I, who have 10 years of blender experience, don't remember all the hotkeys inside the modal tool itself and I have already had problems with tools that work like that.

I recommend to look at this proposal very supported by the users of how the header area should be improved, and not to insist on changing everything to a statusbar what only create problems to the users.

https://blender.community/c/rightclickselect/Bldbbc/

image.png

I think this idea is a mistake. All information must appear in the header area. You can't separate the parameter from the shorcut needed to change it and you have to be passing from one bar to another to know which hotkey is the one you have to press. Even I, who have 10 years of blender experience, don't remember all the hotkeys inside the modal tool itself and I have already had problems with tools that work like that. I recommend to look at this proposal very supported by the users of how the header area should be improved, and not to insist on changing everything to a statusbar what only create problems to the users. https://blender.community/c/rightclickselect/Bldbbc/ ![image.png](https://archive.blender.org/developer/F8304611/image.png)

Added subscriber: @3di

Added subscriber: @3di

Status bar isn't big enough for keymaps. Even on my 4K monitor there's not enough room for even a small number of keymaps to be visible if I have the other status bar information options enabled (which I do). It's not a good idea to hide some of the keymaps, whose to say what a person might need to know, and the keymaps must be important enough to show, otherwise they wouldn't have been created in the first place.

Best solution move the keymaps to the side of the 3d viewport opposite to the header, and combine them with the curent values like @AlbertoVelazquez suggests. This way it won't be fighting with the header, it won't be limited to a too small space, and the user won't have to look between two different places to see the value and the required keymap to change it.

Status bar isn't big enough for keymaps. Even on my 4K monitor there's not enough room for even a small number of keymaps to be visible if I have the other status bar information options enabled (which I do). It's not a good idea to hide some of the keymaps, whose to say what a person might need to know, and the keymaps must be important enough to show, otherwise they wouldn't have been created in the first place. Best solution move the keymaps to the side of the 3d viewport opposite to the header, and combine them with the curent values like @AlbertoVelazquez suggests. This way it won't be fighting with the header, it won't be limited to a too small space, and the user won't have to look between two different places to see the value and the required keymap to change it.

Added subscriber: @tintwotin

Added subscriber: @tintwotin

This comment was removed by @tintwotin

*This comment was removed by @tintwotin*

There are also wrong shortcuts in the Statusbar: https://developer.blender.org/T83307

There are also wrong shortcuts in the Statusbar: https://developer.blender.org/T83307
Philipp Oeser removed the
Interest
User Interface
label 2023-02-10 09:26:13 +01:00
Brecht Van Lommel added this to the User Interface project 2024-02-13 19:12:39 +01:00
Brecht Van Lommel changed title from Improve keymap display in status bar to Consistent and improved modal operator status display 2024-02-13 19:13:32 +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
6 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#56599
No description provided.