Inconsistent input drag editing #111195

Open
opened 2023-08-17 02:17:02 +02:00 by Guillermo Venegas · 6 comments
Contributor

System Information
Operating system:
Graphics card:

Blender Version
Broken:
Worked:

Short description of error
Some inputs that allows editing whit mouse drag can change values with any drag movement, and the will be clamped to
min-max values, but other inputs relies on mouse position rather that the drag movement, this makes that if the user makes a drag beyond bounds, to be able to edit the values the user need to move the mouse again within the bounds of the input, that is not necessary because mouse is not visible.

Exact steps for others to reproduce the error

  1. Use the color picker and move the mouse to the left beyond limits
  2. Move the mouse to the right, see that there not instantly a value change, the invisible mouse need to enters within bounds

Here in the video, i edited the surface radius and is is visible that any movement changes the value
But for Surface the mouse need to be reallocated in the input box
Also for color picker
Important Note: I force to show the mouse to see the actual mouse movement, using the slider or color picker without knowing where the mouse is makes it feel weird

**System Information** Operating system: Graphics card: **Blender Version** Broken: Worked: **Short description of error** Some inputs that allows editing whit mouse drag can change values with any drag movement, and the will be clamped to min-max values, but other inputs relies on mouse position rather that the drag movement, this makes that if the user makes a drag beyond bounds, to be able to edit the values the user need to move the mouse again within the bounds of the input, that is not necessary because mouse is not visible. **Exact steps for others to reproduce the error** 1. Use the color picker and move the mouse to the left beyond limits 2. Move the mouse to the right, see that there not instantly a value change, the invisible mouse need to enters within bounds Here in the video, i edited the surface radius and is is visible that any movement changes the value But for Surface the mouse need to be reallocated in the input box Also for color picker Important Note: **I force to show the mouse** to see the actual mouse movement, using the slider or color picker without knowing where the mouse is makes it feel weird <video src="/attachments/213288b4-4546-4f45-af4a-50a313b54e7d" title="2023-08-16 17-58-31.mp4" controls></video>
Guillermo Venegas added the
Type
Report
Priority
Normal
Status
Needs Triage
labels 2023-08-17 02:17:03 +02:00
Member

Hi @guishe I think this is by design. The "ranged" slider will match the range length to the mouse X movement so the blue section position stays fixed offset relative to your mouse pointer, while the free slider (without min-max) will use RNA property step on mouse move, and it doesn't care about the absolute position of your mouse pointer. You can drag that panel wider to see the effect more prominently.

Hi @guishe I think this is by design. The "ranged" slider will match the range length to the mouse X movement so the blue section position stays fixed offset relative to your mouse pointer, while the free slider (without min-max) will use RNA property step on mouse move, and it doesn't care about the absolute position of your mouse pointer. You can drag that panel wider to see the effect more prominently.
YimingWu added
Module
User Interface
Status
Needs Info from Developers
and removed
Status
Needs Triage
labels 2023-08-17 04:26:42 +02:00
Author
Contributor

both tested have min-max
Are the PROP_FACTOR inputs that depends on mouse position rather than movement

both tested have min-max Are the PROP_FACTOR inputs that depends on mouse position rather than movement

The color picker clearly shows what's going on - you select the color right under the cursor.

The "slider" works in the same way:

slider.gif

The only issue is that in Blender the "slider" is not in its purest form, it's kind of half a "numeric field", but still by design it's a slider.

Though no, the second issue is that the cursor is hidden, which makes the whole thing weird. It's still not a bug, though.

The color picker clearly shows what's going on - you select the color right **under the cursor**. The "slider" works in the same way: ![slider.gif](/attachments/9a32edcc-c35c-41a5-a830-ace81f341c3b) The only issue is that in Blender the "slider" is not in its purest form, it's kind of half a "numeric field", but still by design it's a slider. Though no, the second issue is that the cursor is hidden, which makes the whole thing weird. It's still not a bug, though.
156 KiB
Member

Humm in this case maybe we could make the cursor visible in properties with PROP_FACTOR? So there's a better visual reference.

Humm in this case maybe we could make the cursor visible in properties with `PROP_FACTOR`? So there's a better visual reference.

Humm in this case maybe we could make the cursor visible in properties with PROP_FACTOR? So there's a better visual reference.

No, it won't work. The slider position (value) does not change on initial mouse press (like a normal slider), but the cursor jumps at the end of the operation. I mean, on a normal slider you can click in a place with the desired value to move the handle. But the Blender's slider will go into edit mode, like numeric field.

Everything is blended in Blender, even the slider with the numeric field. :)
This is a big design-topic, and it's probably been discussed before.

> Humm in this case maybe we could make the cursor visible in properties with `PROP_FACTOR`? So there's a better visual reference. No, it won't work. The slider position (value) does not change on initial mouse press (like a normal slider), but the cursor jumps at the end of the operation. I mean, on a normal slider you can click in a place with the desired value to move the handle. But the Blender's slider will go into edit mode, like numeric field. Everything is blended in Blender, even the slider with the numeric field. :) This is a big design-topic, and it's probably been discussed before.
Author
Contributor

Here a fix for inputs values tagged as PROP_FACTOR
#112004

Here a fix for inputs values tagged as `PROP_FACTOR` https://projects.blender.org/blender/blender/pulls/112004
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#111195
No description provided.