Use widget rollover to hide/add UI feedback #38070
Labels
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
18 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#38070
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In Blender, hovering the cursor over a UI item highlights it. This is quite nice, because it's clear which item will be interacted with when clicked.
However, some of the UI widgets don't give proper feedback when hovering the cursor. For example, number fields highlight the entire widget when hovering over it, even though it consists of three distinct areas (left arrow, text field, right arrow). The problem is that the current highlighting gives a false sense that clicking the button anywhere does the same thing. This can lead to user error and confusion when attempting to interact with these fields.
Also, when buttons have no background (icon only), there's no highlighting and pressed state. This makes it unclear if a button has been pressed or not.
Proposed solution:
Use rollover to hide/add useful feedback:
Number fields:
A moving example of this can be seen below:
(click to view)
Icon-only buttons:
Highlighting can also be added more places, such as the headers in the Properties editor:
(click to view)
Changed status to: 'Open'
Added subscriber: @billrey
Added subscriber: @JonathanWilliamson
Added subscriber: @BartekMoniewski
Added subscriber: @ionarn
Added subscriber: @ideasman42
+1 for this proposal, Blender buttons already highlight when you move your house over them, (file browser too) so I'd consider this in keeping with existing UI design.
There area areas IMHO which are not at all clear (as noted in this proposal), Number fields are the most obvious example - other suggestions in this proposal I'd consider lower priority but still worth doing.
This looks good to me.
Added subscriber: @michaelknubben
Rather than completely hiding things such as the arrows, how about just dimming them? I find they're valuable in determining what type of field you're looking at. Is it a text-field that happens to contain numbers, is it a dropdown, is it a numeric field with arrows?
Added subscriber: @PawelLyczkowski-1
Added subscriber: @mont29
Added subscriber: @forest-ka
Added subscriber: @Luarvik
Added subscriber: @CodeManX
This would make it clearer to the user what to expact (data input or increment/decrement step?) and solve the problem with arrow button area:
http://lists.blender.org/pipermail/bf-committers/2014-February/042875.html
But the numbers are aligned to the right now, making the arrows on both sides look a odd / unbalanced. I tried to improve on billrey's mockup and reduce the distance needed to step up/down by moving the arrows next to each other (as seen on OSX for scrollbars for instance):
Added subscriber: @pablovazquez
Added subscriber: @plasmasolutions
Added subscriber: @natecraddock
Added subscriber: @JulianEisel
Added subscriber: @MikePan
Added subscriber: @Januz
Removed subscriber: @natecraddock
Changed status from 'Open' to: 'Archived'