Make All Operators Accessible from Menus #76227

Open
opened 2020-04-29 14:51:30 +02:00 by Campbell Barton · 53 comments

This task proposes all operators should be available in menus.

As of 2.90, the operator search functionality no longer lists all available operators, instead, it expends menus, see #74157 (Use menus for operator search & various improvements).

From replies to this task, some users/developers were only accessing operators via search, so scanning menus made some operators un-searchable.

Instead of considering this something to be fixed, this task proposes that operators which users may want to access from search, also be included in menus.

Notes

  • Popovers could be included in the menu search as well.

Exceptions

  • Internal operators (operators with INTERNAL flag set).
  • User interface operators (re-ordering constraints, modifiers for e.g).
  • Some interactive operators which only make sense to activate interactively (SCULPT_OT_brush_stroke).
  • Operators which don't work or don't make sense in the given context (operators from other editors, other modes etc)

Status

There is a utility to report operators not yet exposed by menu search.

This can be generated using: ./source/tools/utils_maintenance/blender_menu_search_coverage.py

This paste shows it's output at the time of writing P1618

This task proposes all operators should be available in menus. As of 2.90, the operator search functionality no longer lists all available operators, instead, it expends menus, see #74157 (Use menus for operator search & various improvements). From replies to this task, some users/developers were only accessing operators via search, so scanning menus made some operators un-searchable. Instead of considering this something to be fixed, this task proposes that operators which users may want to access from search, also be included in menus. **Notes** - Popovers could be included in the menu search as well. ------- **Exceptions** - Internal operators (operators with `INTERNAL` flag set). - User interface operators (re-ordering constraints, modifiers for e.g). - Some interactive operators which only make sense to activate interactively (`SCULPT_OT_brush_stroke`). - Operators which don't work or don't make sense in the given context (operators from other editors, other modes etc) ------ **Status** There is a utility to report operators not yet exposed by menu search. This can be generated using: `./source/tools/utils_maintenance/blender_menu_search_coverage.py` This paste shows it's output at the time of writing [P1618](https://archive.blender.org/developer/P1618.txt)
Author
Owner

Added subscriber: @ideasman42

Added subscriber: @ideasman42

#87624 was marked as duplicate of this issue

#87624 was marked as duplicate of this issue

#85036 was marked as duplicate of this issue

#85036 was marked as duplicate of this issue

#84411 was marked as duplicate of this issue

#84411 was marked as duplicate of this issue

#82229 was marked as duplicate of this issue

#82229 was marked as duplicate of this issue

#82023 was marked as duplicate of this issue

#82023 was marked as duplicate of this issue

#81936 was marked as duplicate of this issue

#81936 was marked as duplicate of this issue

#81882 was marked as duplicate of this issue

#81882 was marked as duplicate of this issue

#81760 was marked as duplicate of this issue

#81760 was marked as duplicate of this issue

blender/blender-addons#80914 was marked as duplicate of this issue

blender/blender-addons#80914 was marked as duplicate of this issue

blender/blender-addons#80879 was marked as duplicate of this issue

blender/blender-addons#80879 was marked as duplicate of this issue

#80573 was marked as duplicate of this issue

#80573 was marked as duplicate of this issue

#80503 was marked as duplicate of this issue

#80503 was marked as duplicate of this issue

#80449 was marked as duplicate of this issue

#80449 was marked as duplicate of this issue

#80413 was marked as duplicate of this issue

#80413 was marked as duplicate of this issue

blender/blender-addons#80345 was marked as duplicate of this issue

blender/blender-addons#80345 was marked as duplicate of this issue

blender/blender-addons#80152 was marked as duplicate of this issue

blender/blender-addons#80152 was marked as duplicate of this issue

blender/blender-addons#76256 was marked as duplicate of this issue

blender/blender-addons#76256 was marked as duplicate of this issue
Campbell Barton changed title from Include All Operators in Menus to Make All Operators Accessible from Menus 2020-04-29 14:52:32 +02:00

Added subscriber: @TheRedWaxPolice

Added subscriber: @TheRedWaxPolice

Hi.
Can the active tools and brushes (from toolbar) be made searchable too? They are not in the menus, so we can't search them...
I think it would make the search function more powerful and complete...

Hi. Can the active tools and brushes (from toolbar) be made searchable too? They are not in the menus, so we can't search them... I think it would make the search function more powerful and complete...

Added subscriber: @WilliamReynish

Added subscriber: @WilliamReynish

@TheRedWaxPolice This is not a regression - you could never activate active tools using operator search, nor does it make any sense. An active tool is not a menu item or command. You could also ask why you can't set any property from menu search, but likewise it's outside the scope of what this feature is for.

@TheRedWaxPolice This is not a regression - you could never activate active tools using operator search, nor does it make any sense. An active tool is not a menu item or command. You could also ask why you can't set any property from menu search, but likewise it's outside the scope of what this feature is for.

In #76227#920152, @WilliamReynish wrote:
This is not a regression

Maybe not, but it would be a great improvement for sure...

you could never activate active tools using operator search, nor does it make any sense.

Why not?
Besides making a lot of sense IMO, this is how the search function works in most 3D software. It's very common to search and activate tools from there. I can't see why Blender's search function can't be as equally powerful...

it's outside the scope of what this feature is for.

Sorry then... I guess I just wanted to see some improvements in this area...

Cheers..

> In #76227#920152, @WilliamReynish wrote: >This is not a regression Maybe not, but it would be a great improvement for sure... >you could never activate active tools using operator search, nor does it make any sense. Why not? Besides making a lot of sense IMO, this is how the search function works in most 3D software. It's very common to search and activate tools from there. I can't see why Blender's search function can't be as equally powerful... >it's outside the scope of what this feature is for. Sorry then... I guess I just wanted to see some improvements in this area... Cheers..
Member

Added subscriber: @Mets

Added subscriber: @Mets
Member

Added subscribers: @ThatAsherGuy, @DanPool

Added subscribers: @ThatAsherGuy, @DanPool
Member

It is nice to see this task.

I guess these comments from the previous thread are relevant:

In #74157#911479, @ThatAsherGuy wrote:
If we could tag menus as searchable/non-searchable, most of those issues would go away. Add-on developers could then use searchable menus that aren't exposed through the UI to register aliases without adding clutter, and tag their convenience menus and pie menus as non-searchable to limit the number of duplicate search entries.

In #74157#915176, @DanPool wrote:
addon developers can only prepend or append to existing menus, meaning all addon operators will be piled up at the beginning or end of menus meaning you will have to scroll well into the middle of the menu before you get to builtin operators. Or developers have to create their own menu, meaning the menu bar will become huge and unmanagable.

And to add to the latter, I think if we are forcing addon developers to put their buttons in menus, it is fair to expect that support for their ability to do so would increase. The ability to look through a built-in menu and add your button specifically before or after an existing button, I think is essential.

It is nice to see this task. I guess these comments from the previous thread are relevant: > In #74157#911479, @ThatAsherGuy wrote: > If we could tag menus as searchable/non-searchable, most of those issues would go away. Add-on developers could then use searchable menus that aren't exposed through the UI to register aliases without adding clutter, and tag their convenience menus and pie menus as non-searchable to limit the number of duplicate search entries. > In #74157#915176, @DanPool wrote: > addon developers can only prepend or append to existing menus, meaning all addon operators will be piled up at the beginning or end of menus meaning you will have to scroll well into the middle of the menu before you get to builtin operators. Or developers have to create their own menu, meaning the menu bar will become huge and unmanagable. And to add to the latter, I think if we are forcing addon developers to put their buttons in menus, it is fair to expect that support for their ability to do so would increase. The ability to look through a built-in menu and add your button specifically before or after an existing button, I think is essential.
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Note we are also getting reports for Addons (e.g. blender/blender-addons#76256 (Object Scatter doesnt show up in operator search))

Note we are also getting reports for Addons (e.g. blender/blender-addons#76256 (Object Scatter doesnt show up in operator search))

Added subscriber: @RC12

Added subscriber: @RC12

Added subscriber: @amdj1

Added subscriber: @amdj1

Added subscriber: @rjg

Added subscriber: @rjg

Given that 2.90 is close to being released, I'm assuming this is postponed to 2.91?

Given that 2.90 is close to being released, I'm assuming this is postponed to 2.91?

Added subscriber: @Tauo19

Added subscriber: @Tauo19

I have been following the conversation about the scatter function disappearing from F3 in 2.9 (latest build). There was a reference to this area of discussion in the conversation. Any news on scatter being re-implemented?

Apologies if this is not the correct place to ask this question

I have been following the conversation about the scatter function disappearing from F3 in 2.9 (latest build). There was a reference to this area of discussion in the conversation. Any news on scatter being re-implemented? Apologies if this is not the correct place to ask this question
Member
Added subscribers: @Basarchitects, @JrmSpirit, @Alaska, @JacquesLucke
Member

Added subscriber: @vicen

Added subscriber: @vicen
Member

For those experiencing issues with some operators not showing up in the search operator window, try these steps:

  1. From the top of Blender select Edit -> Preferences.
  2. From the list of tabs on the left, select Interface.
  3. Enable the option Developer Extras in the Display section of the .
  4. Save user preferences by clicking on the three horizontal lines in the bottom left and selecting Save Preferences. Now you should be able to find the operator you're looking for in the search operator window F3.

This is just a temporary fix. As this task explains (#76227), almost everything in Blender should be updated so they're accessable in the search operator without adjusting settings. But until then, this is a work around.

For those experiencing issues with some operators not showing up in the search operator window, try these steps: 1. From the top of Blender select `Edit -> Preferences`. 2. From the list of tabs on the left, select `Interface`. 3. Enable the option `Developer Extras` in the `Display` section of the . 4. Save user preferences by clicking on the three horizontal lines in the bottom left and selecting `Save Preferences`. Now you should be able to find the operator you're looking for in the search operator window `F3`. This is just a temporary fix. As this task explains (#76227), almost everything in Blender should be updated so they're accessable in the search operator without adjusting settings. But until then, this is a work around.
Member

Added subscriber: @Miketche

Added subscriber: @Miketche

Removed subscriber: @RC12

Removed subscriber: @RC12
Member

Added subscriber: @mzrdesign

Added subscriber: @mzrdesign

Added subscriber: @gbendana

Added subscriber: @gbendana
Member

Added subscriber: @k-pasta

Added subscriber: @k-pasta
Member

To everyone coming here because of the Scatter Objects operator: this has just been added to the menus: blender/blender-addons@df0fa2341e

To everyone coming here because of the Scatter Objects operator: this has just been added to the menus: blender/blender-addons@df0fa2341e
Member

Added subscriber: @HongTakJang

Added subscriber: @HongTakJang

Added subscriber: @immozzer-3

Added subscriber: @immozzer-3
Member

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

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

Added subscriber: @sorinv

Added subscriber: @sorinv

Added subscriber: @SimonStorl-Schulke

Added subscriber: @SimonStorl-Schulke

Added subscriber: @roobol

Added subscriber: @roobol

Added subscriber: @jhofmann

Added subscriber: @jhofmann

Added subscriber: @DougRichardson

Added subscriber: @DougRichardson

Added subscriber: @Coverop

Added subscriber: @Coverop
Member

Added subscriber: @aztec

Added subscriber: @aztec
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
11 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#76227
No description provided.