Show Pie Menu quadrants #75821

Open
opened 2020-04-17 11:45:22 +02:00 by William Reynish · 14 comments

We have received a few bug reports like #59102 and #74880, in which users are confused by the current design of the pie menus.

The issue is that when the cursor is over or close to certain areas of titles, the item that is highlighted is not always what the user expects based on the current pie UI:

Screenshot 2020-04-17 at 11.25.04.png

Even though the cursor is closer to Bottom,View Camera is highlighted, and will get executed when clicking or dismissing the pie menu.

This animated Gif also shows the issue very clearly:
YKq0rSm1y1.gif

This issue stems from poor visual design. The current UI doesn't communicate to users that pie menus are not a radial arrangement of buttons, but really they are a series of equal quadrants (pie pieces):

Screenshot 2020-04-17 at 11.28.36.png

This is essential to make pie menus fast to operate, because then you can use then via a gesture to quickly execute commands.

We can solve this in a few ways. The simplest solution could be to highlight the currently active pie quadrant:

Screenshot 2020-04-17 at 11.50.07.png

Then it becomes clear why View Camera is executed while the cursor is in this position.

We can also make changes to the pie menu centers, to help communicate how many pie pieces there are, and which quadrant the cursor is currently in.

Currently it looks like this:
Screenshot 2020-04-17 at 11.37.32.png

It tells you very roughly where the cursor is, but not which quadrant it is in, nor how many quadrants there are.

With a few changes, it can be a lot more helpful:

Screenshot 2020-04-17 at 11.43.36.png

  • More accurate display of where the cursor is
  • The number of quadrants are communicated via the tick marks, like on a watch face
  • You can see in which quadrant the cursor is
We have received a few bug reports like #59102 and #74880, in which users are confused by the current design of the pie menus. The issue is that when the cursor is over or close to certain areas of titles, the item that is highlighted is not always what the user expects based on the current pie UI: ![Screenshot 2020-04-17 at 11.25.04.png](https://archive.blender.org/developer/F8478365/Screenshot_2020-04-17_at_11.25.04.png) Even though the cursor is closer to *Bottom*,*View Camera* is highlighted, and will get executed when clicking or dismissing the pie menu. This animated Gif also shows the issue very clearly: ![YKq0rSm1y1.gif](https://archive.blender.org/developer/F8478401/YKq0rSm1y1.gif) This issue stems from poor visual design. The current UI doesn't communicate to users that pie menus are *not* a radial arrangement of buttons, but really they are a series of equal quadrants (pie pieces): ![Screenshot 2020-04-17 at 11.28.36.png](https://archive.blender.org/developer/F8478370/Screenshot_2020-04-17_at_11.28.36.png) This is essential to make pie menus fast to operate, because then you can use then via a gesture to quickly execute commands. We can solve this in a few ways. The simplest solution could be to highlight the currently active pie quadrant: ![Screenshot 2020-04-17 at 11.50.07.png](https://archive.blender.org/developer/F8478405/Screenshot_2020-04-17_at_11.50.07.png) Then it becomes clear why *View Camera* is executed while the cursor is in this position. We can also make changes to the pie menu centers, to help communicate how many pie pieces there are, and which quadrant the cursor is currently in. Currently it looks like this: ![Screenshot 2020-04-17 at 11.37.32.png](https://archive.blender.org/developer/F8478391/Screenshot_2020-04-17_at_11.37.32.png) It tells you very roughly where the cursor is, but not which quadrant it is in, nor how many quadrants there are. With a few changes, it can be a lot more helpful: ![Screenshot 2020-04-17 at 11.43.36.png](https://archive.blender.org/developer/F8478398/Screenshot_2020-04-17_at_11.43.36.png) - More accurate display of where the cursor is - The number of quadrants are communicated via the tick marks, like on a watch face - You can see in which quadrant the cursor is
William Reynish self-assigned this 2020-04-17 11:45:22 +02:00

Added subscriber: @WilliamReynish

Added subscriber: @WilliamReynish

Added subscriber: @DuarteRamos

Added subscriber: @DuarteRamos

Added subscriber: @Russ1642

Added subscriber: @Russ1642

Added subscriber: @ckohl_art

Added subscriber: @ckohl_art

The blue dot is pretty small. If the segment itself lit up with a highlight color it might be easier to see at a glance.

image.png

(Probably not with that yellow color but it illustrates the idea.)

The blue dot is pretty small. If the segment itself lit up with a highlight color it might be easier to see at a glance. ![image.png](https://archive.blender.org/developer/F8488867/image.png) (Probably not with that yellow color but it illustrates the idea.)

Alternative design, with different tradeoffs:

This leans even more into the pie/pie piece concept, but is a much bigger change:

Screenshot 2020-04-22 at 13.49.23-2.png

Alternative design, with different tradeoffs: This leans even more into the pie/pie piece concept, but is a much bigger change: ![Screenshot 2020-04-22 at 13.49.23-2.png](https://archive.blender.org/developer/F8489269/Screenshot_2020-04-22_at_13.49.23-2.png)

Added subscriber: @lamoot

Added subscriber: @lamoot

Added subscriber: @hadrien

Added subscriber: @hadrien

In #75821#915530, @WilliamReynish wrote:
Alternative design, with different tradeoffs:

This leans even more into the pie/pie piece concept, but is a much bigger change:

Screenshot 2020-04-22 at 13.49.23-2.png

It's definitely clearer but also obstructs the view quite a bit. Maybe the quadrant overlay can keep the gradient as in your previous mockups, and have the separators as an additional hint. I don't think it's necessary to keep the small "cursor" indicator, it seems redundant to me (I usually know where my cursor is relative to the pie menu). Yes I did leave it in this mockup.

mockup_pie_menu_quadrants.png

Also some pie menu entries can be verbose enough to overflow into the next quadrant, your mockup does not show how it would look in such a situation without the usual buttons : would text wrap so as to stay contained inside the quadrant ?

> In #75821#915530, @WilliamReynish wrote: > Alternative design, with different tradeoffs: > > This leans even more into the pie/pie piece concept, but is a much bigger change: > > ![Screenshot 2020-04-22 at 13.49.23-2.png](https://archive.blender.org/developer/F8489269/Screenshot_2020-04-22_at_13.49.23-2.png) It's definitely clearer but also obstructs the view quite a bit. Maybe the quadrant overlay can keep the gradient as in your previous mockups, and have the separators as an additional hint. I don't think it's necessary to keep the small "cursor" indicator, it seems redundant to me (I usually know where my cursor is relative to the pie menu). Yes I did leave it in this mockup. ![mockup_pie_menu_quadrants.png](https://archive.blender.org/developer/F8516343/mockup_pie_menu_quadrants.png) Also some pie menu entries can be verbose enough to overflow into the next quadrant, your mockup does not show how it would look in such a situation without the usual buttons : would text wrap so as to stay contained inside the quadrant ?
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

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

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

Since we are far into the discussion, I think we can confirm this?
(not completely sure about the meaning of Status of Design tasks, but Needs Triage seems to be the wrong status here...)

Since we are far into the discussion, I think we can confirm this? (not completely sure about the meaning of `Status` of `Design` tasks, but Needs Triage seems to be the wrong status here...)

Added subscriber: @wevon-2

Added subscriber: @wevon-2

When the radius is small they are more compact and the visual effort is less, but they are misaligned. I have made a simulation with Constraints so that you can check a new alignment.
{F8661186}PieQuadrant.png
Incidentally I think that although it does not solve, but it slightly improves the problem of quadrants, if their proportion varies.
On the left the proposal, on the right the current one.
Scale the octagon to modify the radius.
PieAligned.blend

Regarding the issue of visual fatigue, I have proven that playing pairs games with cards, I win my children when they are grouped, but I lose when they are separated, since the route is longer and they are faster.

When the radius is small they are more compact and the visual effort is less, but they are misaligned. I have made a simulation with Constraints so that you can check a new alignment. {[F8661186](https://archive.blender.org/developer/F8661186/PieAligned.png)}![PieQuadrant.png](https://archive.blender.org/developer/F8661188/PieQuadrant.png) Incidentally I think that although it does not solve, but it slightly improves the problem of quadrants, if their proportion varies. On the left the proposal, on the right the current one. Scale the octagon to modify the radius. [PieAligned.blend](https://archive.blender.org/developer/F8661195/PieAligned.blend) Regarding the issue of visual fatigue, I have proven that playing pairs games with cards, I win my children when they are grouped, but I lose when they are separated, since the route is longer and they are faster.
Philipp Oeser removed the
Interest
User Interface
label 2023-02-10 09:24:42 +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
8 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#75821
No description provided.