Making the mode selection dropdown list in the Editor headers consistent across all editors that use them #38254
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#38254
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?
The mode selection dropdown lists are inconsistent across the editor headers that use them (3D view, Graph, Dopesheet, Image, MCE, Outliner).
I have started working on this already. A lot of the inconsistency is caused by the 3D view header being called and executed in a different way from the other headers.
The reason why I am raising this task is to validate the proposed changes being:
Proposed 3D view tooltips:
OBJECT: "Manipulate objects",
EDIT: "Edit object mesh or armature"
SCULPT: "Edit mesh using sculpt tools"
VERTEX_PAINT: "Paint object's vertices"
WEIGHT_PAINT: "Edit object's vertex weights"
TEXTURE_PAINT: "Paint on object's selected UV Map"
PARTICLE_EDIT: "Edit particle system using brushes"
POSE: "Transform bones in armature"
Changed status to: 'Open'
Added subscriber: @WarrenBahler
good points here, some things I just noticed in the UV image editor; in the paint and mask modes, and uv sculpt mode; the tools are activated at the bottom of the tool panel, making the switch between modes almost invisible. the user must then scroll past task unrelated tools, to reach the primary tools of the mode. this might be improve with the toolbar tabs implemented though.
also I think a dedicated "UV Editing" mode, would be best, currently the "view" mode is not really adequate: most of the tools in the toolbar are unrelated to UV editing, and the UV tools are only accessible by menus.
I would suggest a separate "UV Edit" mode, with more relevant tools displayed, like sculpt tools and something like this addon here: blender/blender-addons#37975
Added subscriber: @BartekMoniewski
Great proposal. I was thinking about something like that few months ago. IMHO this topic is more complicated than just naming conventions and tooltips. We need a hierarchical structure and guidlines for whole blender interface, not just modes. Even for experienced users things can be confusing.
For now there is no strict separation what is editor, editor mode, item type or view type. Not from user point of view. 3D view is most intuitive right now but nodes, image or movie clip editors are very inconsistent across each others.
Also Headers priority is not high enough. In fact from clarity point of view they are most important interface items in blender. Items in headers are not arranged in logical way. Going from left to right we have Editor Type (good), then Editor Menus that are related mostly to mode and then Editor Mode. Changing editor mode alter menu contents but menus are theoretically higher in hierarchy.
Next catchy thing. In node editor node tree types are displayed as icons not as dropdown list. In fact editing materials and compositing are completely different topics, users don't change this modes often while working. Those things need to be displayed as separate editor modes, just like editing F-Curve and Drivers in Graph editor. Same methods but completely different and non strictly related tasks.
I propose to establish a tree structure of interface items that users can easily learn and to be able to translate experience from one editor window to another.
Things should look like that:
Going this way arrangement of items in Headers should look like that:
With that approach we can achieve logical order of items consistent with all editor types and modes. We first need to create tree structure of editor window typed and editor modes with all interface items and make documentation for users and developers.
Added subscribers: @JonathanWilliamson, @AndrewPrice, @billrey, @brecht, @ideasman42, @ThomasDinges, @PawelLyczkowski-1
Hi,
Thanks for the thoughts, but I got stuck at #3. The 3D View mode selector uses different code from the others (there's a lot more C involved) and I have less time now than I did in January (my summer). So at the moment I'm on hold on this item.
Good suggestions, but I suspect someone else will need to pick them up and run with them...
Apologies if I got your hopes up...
Added subscriber: @ionarn
Added subscriber: @mont29
Changed status from 'Open' to: 'Archived'
No resolution or activity in over 3 months,
archiving, listed in the wiki .
Can re-open when we have time to handle this one.