Menu Editor for Quick Favorites #73178

Open
opened 2020-01-17 10:08:21 +01:00 by Campbell Barton · 58 comments

Currently users can only manage menu items in the quick-favorites menu by adding/removing items.

This task proposes to:

  • Create a generic menu editor in the user preferences.

    • Add/remove menu items
    • Re-ordering menu items.
    • Operators options should be able to be changed or unset - as we have with the keymap editor.

Implementation

  • This could share UI code with the keymap editor for adjusting operator settings, since internally they are very similar.
  • We may support multiple kinds of menus, besides "Quick Favorites", internally there is support for this. Even if this isn't exposed to users initially.
This would be useful for declaring user defined toolbars for example.

User Interface
Here's how the UI could be organized:

{F8282863, size=full}

Currently users can only manage menu items in the quick-favorites menu by adding/removing items. This task proposes to: - Create a generic menu editor in the user preferences. - Add/remove menu items - Re-ordering menu items. - Operators options should be able to be changed or unset - as we have with the keymap editor. **Implementation** - This could share UI code with the keymap editor for adjusting operator settings, since internally they are very similar. - We may support multiple kinds of menus, besides "Quick Favorites", internally there is support for this. Even if this isn't exposed to users initially. ``` This would be useful for declaring user defined toolbars for example. ``` **User Interface** Here's how the UI could be organized: {[F8282863](https://archive.blender.org/developer/F8282863/Screenshot_2020-01-17_at_11.08.58.png), size=full}
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

Here's a fairly quick mockup to show the concept:

Screenshot 2020-01-17 at 10.37.16.png

Here's a fairly quick mockup to show the concept: ![Screenshot 2020-01-17 at 10.37.16.png](https://archive.blender.org/developer/F8282818/Screenshot_2020-01-17_at_10.37.16.png)
Author
Owner

@WilliamReynish looks good, prefer this to the keymap style UI which I find tends towards too much scrolling, getting slow at times too.

@WilliamReynish looks good, prefer this to the keymap style UI which I find tends towards too much scrolling, getting slow at times too.

Added subscriber: @DuarteRamos

Added subscriber: @DuarteRamos

This layout makes better use of available space:

Screenshot 2020-01-17 at 11.08.58.png

This layout makes better use of available space: ![Screenshot 2020-01-17 at 11.08.58.png](https://archive.blender.org/developer/F8282863/Screenshot_2020-01-17_at_11.08.58.png)
Member

Added subscriber: @JulianEisel

Added subscriber: @JulianEisel
Member

Did you consider making it more like the keymap editor layout? Where you have a list of boxes that you can expand for the options.

Not saying that we should take the keymap editor as example of good design, but I think its layout is generally okay.
Otherwise it does feel a bit inconsistent, so I'm just wondering if it was considered.

Did you consider making it more like the keymap editor layout? Where you have a list of boxes that you can expand for the options. Not saying that we should take the keymap editor as example of good design, but I think its layout is generally okay. Otherwise it does feel a bit inconsistent, so I'm just wondering if it was considered.

@JulianEisel That was the first thing I did in fact :)

But Campbell pointed out that it probably makes it harder to navigate, and seeing multiple lists at once isn't likely to be that useful. Some ops have many options, which would mean lots and lots of scrolling, and lots of opening and closing panels.

Here's the first mockup:
Screenshot 2020-01-17 at 11.26.22.png

However, your point stands that it is a bit inconsistent. One solution of course is to make the keymap editor also work more like this.

@JulianEisel That was the first thing I did in fact :) But Campbell pointed out that it probably makes it harder to navigate, and seeing multiple lists at once isn't likely to be that useful. Some ops have *many* options, which would mean lots and lots of scrolling, and lots of opening and closing panels. Here's the first mockup: ![Screenshot 2020-01-17 at 11.26.22.png](https://archive.blender.org/developer/F8282884/Screenshot_2020-01-17_at_11.26.22.png) However, your point stands that it is a bit inconsistent. One solution of course is to make the keymap editor also work more like this.

Added subscriber: @wevon-2

Added subscriber: @wevon-2

One solution of course is to make the keymap editor also work more like this.

I vote it
The only drawback I see is when comparing options.
If not all of the preference editors were synchronized, it would be resolved, they are currently a clone.

> One solution of course is to make the keymap editor also work more like this. I vote it The only drawback I see is when comparing options. If not all of the preference editors were synchronized, it would be resolved, they are currently a clone.

Added subscriber: @ThatAsherGuy

Added subscriber: @ThatAsherGuy
Author
Owner

In #73178#851730, @wevon-2 wrote:

One solution of course is to make the keymap editor also work more like this.

I vote it
The only drawback I see is when comparing options.
If not all of the preference editors were synchronized, it would be resolved, they are currently a clone.

The keymap editor needs work, although the design hasn't yet been done as far as I know (details should be added to #68884 (Keymap system refactor) eventually).

> In #73178#851730, @wevon-2 wrote: >> One solution of course is to make the keymap editor also work more like this. > I vote it > The only drawback I see is when comparing options. > If not all of the preference editors were synchronized, it would be resolved, they are currently a clone. The keymap editor needs work, although the design hasn't yet been done as far as I know (details should be added to #68884 (Keymap system refactor) eventually).

Added subscriber: @Arin-1

Added subscriber: @Arin-1

Hey! I am new here. Can you tell me something about this project more specifically?

Hey! I am new here. Can you tell me something about this project more specifically?

This comment was removed by @Arin-1

*This comment was removed by @Arin-1*

In this project do we plan to add the quick favorites menu?

In this project do we plan to add the quick favorites menu?

In #73178#851592, @WilliamReynish wrote:
This layout makes better use of available space:

Screenshot 2020-01-17 at 11.08.58.png

I have a suggestion We can add one more small box at the bottom of it. To make room for extra options and components.

> In #73178#851592, @WilliamReynish wrote: > This layout makes better use of available space: > > ![Screenshot 2020-01-17 at 11.08.58.png](https://archive.blender.org/developer/F8282863/Screenshot_2020-01-17_at_11.08.58.png) I have a suggestion We can add one more small box at the bottom of it. To make room for extra options and components.

Added subscriber: @ckohl_art

Added subscriber: @ckohl_art
Member

Added subscriber: @JulienKaspar

Added subscriber: @JulienKaspar

It has to be done using c or c#?

It has to be done using c or c#?

Added subscriber: @A.Lex_3D

Added subscriber: @A.Lex_3D

Without knowing that this proposal already existed I proposed something very similar a few weeks ago on RightClickSelect:
https://blender.community/c/rightclickselect/bpfbbc/

I made a mockup that goes a little more in the direction of an actual menu editor as it would include more than just one menu to add commands on the fly:
image.png
image.png

If this isn't helpful please just disregard it (or delete the comment).

Without knowing that this proposal already existed I proposed something very similar a few weeks ago on RightClickSelect: https://blender.community/c/rightclickselect/bpfbbc/ I made a mockup that goes a little more in the direction of an actual menu editor as it would include more than just one menu to add commands on the fly: ![image.png](https://archive.blender.org/developer/F8398917/image.png) ![image.png](https://archive.blender.org/developer/F8398920/image.png) If this isn't helpful please just disregard it (or delete the comment).
Member

Added subscriber: @Tempo

Added subscriber: @Tempo

Added subscriber: @ooopie

Added subscriber: @ooopie

It would be great if this interface could allow the user to add a custom, multi-line, python operation to their QuickFavorites menu, essentially giving blender basic macro capability, and allowing the user to keep custom operations at their fingertips. (akin to Maya's ability to drag operations onto the 'shelf' creating a custom button)

It would be great if this interface could allow the user to add a custom, multi-line, python operation to their QuickFavorites menu, essentially giving blender basic macro capability, and allowing the user to keep custom operations at their fingertips. (akin to Maya's ability to drag operations onto the 'shelf' creating a custom button)

Added subscriber: @adarshakshat

Added subscriber: @adarshakshat

Added subscriber: @johnsyed

Added subscriber: @johnsyed

Added subscriber: @xan2622

Added subscriber: @xan2622

Are there usage statistics about the Quick Favourites menu? How many entries do Blender users usually add into it?

(just an idea:) Allowing the Quick Favourites menu to feature (up to) 3 columns could be a solution to avoid having a very tall menu.
With a layout a bit similar to the RMB-click menu (3 columns):

3columns.png

Are there usage statistics about the Quick Favourites menu? How many entries do Blender users usually add into it? (just an idea:) Allowing the Quick Favourites menu to feature (up to) 3 columns could be a solution to avoid having a very tall menu. With a layout a bit similar to the RMB-click menu (3 columns): ![3columns.png](https://archive.blender.org/developer/F8524160/3columns.png)

(Another idea:) Allow to make the Quick Favourites Menu different on each workspace.

(Another idea:) Allow to make the *Quick Favourites Menu* different on each workspace.

Added subscriber: @AlexeyPerminov

Added subscriber: @AlexeyPerminov

Added subscriber: @Nominous

Added subscriber: @Nominous

Added subscriber: @MizManFryinPan

Added subscriber: @MizManFryinPan

Added subscriber: @EvandroFerreiradaCosta

Added subscriber: @EvandroFerreiradaCosta

One suggestion is for this to be expanded to allow not only one python command but multiple operations sequentially. Or maybe this could become it's own task in the form of a "Macro editor".
image.png
I'm thinking of this because right now it's a hassle to edit object origins in Edit mode, but the built-in addon 3D Viewport Pie Menus has a pie menu (for both object and edit mode) with the option "Origin to Selected" which basically does three commands sequentially as the image above shows.
And as far as I know it's impossible to add addons functions such as that "Origin to Selected" into the Quick Favorites. Allowing a single command would only permit being able to set a Quick Favorite to open the entire addon pie menu, instead of the specific function inside.

One suggestion is for this to be expanded to allow not only one python command but multiple operations sequentially. Or maybe this could become it's own task in the form of a "Macro editor". ![image.png](https://archive.blender.org/developer/F8699932/image.png) I'm thinking of this because right now it's a hassle to edit object origins in Edit mode, but the built-in addon `3D Viewport Pie Menus` has a pie menu (for both object and edit mode) with the option "Origin to Selected" which basically does three commands sequentially as the image above shows. And as far as I know it's impossible to add addons functions such as that "Origin to Selected" into the Quick Favorites. Allowing a single command would only permit being able to set a Quick Favorite to open the entire addon pie menu, instead of the specific function inside.

Added subscriber: @Thane5

Added subscriber: @Thane5

Added subscriber: @Varyag

Added subscriber: @Varyag

Added subscriber: @Pipeliner

Added subscriber: @Pipeliner

This comment was removed by @Pipeliner

*This comment was removed by @Pipeliner*

Added subscriber: @zNight

Added subscriber: @zNight

Added subscriber: @Elisabeth69

Added subscriber: @Elisabeth69

Added subscriber: @Venryx

Added subscriber: @Venryx

Added subscriber: @wenna666

Added subscriber: @wenna666

this would be massive killer UI feature ,and should be shipped with 3.0.

this would be massive killer UI feature ,and should be shipped with 3.0.

Added subscriber: @Aeraglyx

Added subscriber: @Aeraglyx

It shouldn't be forgotten that this feature was already in development on a GSoC project in 2020 on this Branch https://developer.blender.org/diffusion/B/browse/soc-2020-custom-menus/

This is the weekly report thread: https://devtalk.blender.org/t/gsoc-2020-custom-menus-weekly-reports/13721

It shouldn't be forgotten that this feature was already in development on a GSoC project in 2020 on this Branch https://developer.blender.org/diffusion/B/browse/soc-2020-custom-menus/ This is the weekly report thread: https://devtalk.blender.org/t/gsoc-2020-custom-menus-weekly-reports/13721

Added subscriber: @Grady

Added subscriber: @Grady

I'm interested in trying to make an addon to achieve this goal, but I can't find anywhere in the python documentation that points to where I'd go to start editing/reading the quick favourites data, could anyone please give me a pointer if they know where to go to find this?

I'm interested in trying to make an addon to achieve this goal, but I can't find anywhere in the python documentation that points to where I'd go to start editing/reading the quick favourites data, could anyone please give me a pointer if they know where to go to find this?

Added subscriber: @hadouken

Added subscriber: @hadouken

Added subscriber: @Aerie

Added subscriber: @Aerie

Added subscriber: @LahceneB

Added subscriber: @LahceneB

Added subscriber: @FouFao

Added subscriber: @FouFao

Added subscriber: @Wassily

Added subscriber: @Wassily

Added subscriber: @CaptainHexagon

Added subscriber: @CaptainHexagon
Contributor

Added subscriber: @Nika-Kutsniashvili

Added subscriber: @Nika-Kutsniashvili
Philipp Oeser removed the
Interest
User Interface
label 2023-02-10 09:24:52 +01:00

What a shame this code seems to have been abandoned. Really wish this feature would see the daylight

What a shame this code seems to have been abandoned. Really wish this feature would see the daylight
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
36 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#73178
No description provided.