UX: Prevent click-through panels and used header area #92364

Closed
opened 2021-10-20 12:50:48 +02:00 by Pablo Vazquez · 8 comments
Member

The Problem

It's possible to click-through areas of the interface which are not expected to be clicked-through, leading to frustration.
This is not new, as far as I can remember this issue has been around since Region Overlap was introduced back in the days.

Blender 2.79b
{F11320741, size=full, loop}

Blender 3.0 alpha
{F11320307, size=full, loop}

In the 3D Viewport, the following parts marked in red are click-through:
{F11320410, size=full}


Proposal

In order to keep things feasible, preventing the following (in order of importance) areas from click-through would be great as a first milestone.

  • Panels and sub-panels.
Background only, headers work properly and can't be clicked-through. *This is the highest priority*.
  • Sidebar Tabs. Not only the background of the tabs area, but click-drag on tabs actually runs the active tool (Select Box by default).
  • Used Header/Tool Settings area. I assume this can be tricky so it's listed last. But having some kind of mask around the widgets (including labels) to prevent click-through would solve the issue.
    For a first milestone, preventing clicking through the entire header/tool-settings bar would already be better than the current click-between-widgets behavior.
    Perhaps a quick hack could be to make everything but layout.separator_spacer() not clickable?

{F11320413, size=full}

There are other cases, but to keep things practical, covering what's in this task would be already a huge improvement in usability.

## The Problem It's possible to click-through areas of the interface which are not expected to be clicked-through, leading to frustration. This is not new, as far as I can remember this issue has been around since `Region Overlap` was introduced back in the days. **Blender 2.79b** {[F11320741](https://archive.blender.org/developer/F11320741/sc_-2021-10-20_12.33.12.mp4), size=full, loop} **Blender 3.0 alpha** {[F11320307](https://archive.blender.org/developer/F11320307/sc_-2021-10-20_11.45.06.mp4), size=full, loop} In the 3D Viewport, the following parts marked in red are click-through: {[F11320410](https://archive.blender.org/developer/F11320410/current_click_area.jpg), size=full} ----- ## Proposal In order to keep things feasible, preventing the following (in order of importance) areas from click-through would be great as a first milestone. * **Panels and sub-panels**. ``` Background only, headers work properly and can't be clicked-through. *This is the highest priority*. ``` * **Sidebar Tabs**. Not only the background of the tabs area, but click-drag on tabs actually runs the active tool (Select Box by default). * **Used Header/Tool Settings area**. I assume this can be tricky so it's listed last. But having some kind of mask around the widgets (including labels) to prevent click-through would solve the issue. For a first milestone, preventing clicking through the entire header/tool-settings bar would already be better than the current click-between-widgets behavior. Perhaps a quick hack could be to make everything but `layout.separator_spacer()` not clickable? {[F11320413](https://archive.blender.org/developer/F11320413/ideal_click_area.jpg), size=full} There are other cases, but to keep things practical, covering what's in this task would be already a huge improvement in usability.
Author
Member

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

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

Added subscriber: @pablovazquez

Added subscriber: @pablovazquez
Pablo Vazquez changed title from Prevent click-through panels and used header area to UX: Prevent click-through panels and used header area 2021-10-20 12:56:17 +02:00
Author
Member

Added subscriber: @JulienKaspar

Added subscriber: @JulienKaspar
Member

Added subscribers: @ideasman42, @JulianEisel

Added subscribers: @ideasman42, @JulianEisel
Member

Was facing some related problems while working on #92501, which made me realize what's probably the issue here.
There are two things to ensure:

  • Handle regions in the order as visible on screen. Practically this just means handling overlapping regions before non-overlapping ones.
  • Don't handle any other regions after having found one containing the mouse pointer.

P2573 is a quick & dirty patch for this. Would be good to have someone test it to see if there are other issues caused by it.
For a proper patch I'd like to add a way to iterate over regions so that overlapped regions are first. This one just iterates over regions twice.
@ideasman42 do you see any issue with that in principle?

Was facing some related problems while working on #92501, which made me realize what's probably the issue here. There are two things to ensure: * Handle regions in the order as visible on screen. Practically this just means handling overlapping regions before non-overlapping ones. * Don't handle any other regions after having found one containing the mouse pointer. [P2573](https://archive.blender.org/developer/P2573.txt) is a quick & dirty patch for this. Would be good to have someone test it to see if there are other issues caused by it. For a proper patch I'd like to add a way to iterate over regions so that overlapped regions are first. This one just iterates over regions twice. @ideasman42 do you see any issue with that in principle?
Member

Created a proper version of my earlier patch and submitted it: D13539: UX: Prevent click-through panels and used header area.

Created a proper version of my earlier patch and submitted it: [D13539: UX: Prevent click-through panels and used header area](https://archive.blender.org/developer/D13539).

This issue was referenced by 87c13ac68c

This issue was referenced by 87c13ac68c477486adecd8d548a016309fc2b54d
Member

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Julian Eisel self-assigned this 2022-01-27 18:48:54 +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
3 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#92364
No description provided.