Avoid Dynamic Menu Contents #76212

Open
opened 2020-04-29 06:26:48 +02:00 by Campbell Barton · 4 comments

This tasks proposes that dynamic menu contend could not be used (with some exceptions, below).

Examples of dynamic menu content are menu items that are shown or not based on the number of selected items, an operators poll function, or the saved state of the blend file.

This causes the following problems:

  • Causes User Uncertainty
When you remember a menu item being available and find it missing, it's not obvious whats happening.
If the menu item is greyed out, it makes it obvious the functionality exists but isn't available.
Note that Blender has the ability to set a message for why an operator is disabled which is displayed in the tool-tip *(this should be used more often).*
  • Complicates Documentation
When instructions give steps to perform an action, a user may find the menu item missing, and think they're using the wrong version or the instructions require and add-on or some other customization.
  • Changes Key Accelerators
When menu items change are added/removed, the short-cut keys to activate an item will change too,
so a user can't use muscle memory to activate a menu item. 
  • Complicates Menu Memory
Currently popup menus remember the last action based on the text,
with dynamic changing text, our menu hashing function `ui_popup_menu_memory` would need to somehow support this too, at least if this is used for menu items in popup menus.

Note that even in the case this was solved for updated display-text, moving menu items around has inherent problems with remembering the last used action.

Exceptions

  • Context Menu.
  • Quick Favorites Menu.
  • Menu's that Expand Data such as "Open Recent" or Add "Collection Instances"
This tasks proposes that dynamic menu contend could not be used (with some exceptions, below). Examples of dynamic menu content are menu items that are shown or not based on the number of selected items, an operators poll function, or the saved state of the blend file. This causes the following problems: - **Causes User Uncertainty** ``` When you remember a menu item being available and find it missing, it's not obvious whats happening. ``` ``` If the menu item is greyed out, it makes it obvious the functionality exists but isn't available. ``` ``` Note that Blender has the ability to set a message for why an operator is disabled which is displayed in the tool-tip *(this should be used more often).* ``` - **Complicates Documentation** ``` When instructions give steps to perform an action, a user may find the menu item missing, and think they're using the wrong version or the instructions require and add-on or some other customization. ``` - **Changes Key Accelerators** ``` When menu items change are added/removed, the short-cut keys to activate an item will change too, so a user can't use muscle memory to activate a menu item. ``` - **Complicates Menu Memory** ``` Currently popup menus remember the last action based on the text, with dynamic changing text, our menu hashing function `ui_popup_menu_memory` would need to somehow support this too, at least if this is used for menu items in popup menus. ``` *Note that even in the case this was solved for updated display-text, moving menu items around has inherent problems with remembering the last used action.* **Exceptions** - Context Menu. - Quick Favorites Menu. - Menu's that Expand Data such as "Open Recent" or Add "Collection Instances"
Author
Owner

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Author
Owner

Added subscriber: @ideasman42

Added subscriber: @ideasman42

Added subscriber: @WilliamReynish

Added subscriber: @WilliamReynish

The obvious exceptions are the context menus and the user-defined Quick Favorites.

The obvious exceptions are the context menus and the user-defined Quick Favorites.
Philipp Oeser removed the
Interest
User Interface
label 2023-02-10 09:24:30 +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
2 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#76212
No description provided.