Drag Treashold parameter - no reaction #61260
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#61260
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?
System Information
Operating system: Win 7 64
Graphics card: NV GTX 770
Blender Version
Broken: 2.80,
8c87af7440
, 06.02.2019In my case to the "Front" view I assigned "2" key and to the "Back" view key "2+Drag".
as you can see in the video below, changing the "Drag Threshold" parameter does not bring any effect and blender still uses default value.
I also propose to increase the maximum value from 40 to 1024 px similar to "Tweak Threshold".
Thank you.
Video:
https://www.youtube.com/watch?v=hTS72Ckw5KM&feature=youtu.be
Added subscriber: @Nanomanpro
Added subscriber: @ideasman42
Note, it's using tweak threshold, would be careful changing this since we might not want to have different values for tweak & drag in the event handling (could cause bugs).
Changed status from 'Open' to: 'Archived'
The naming might be poor, but the Drag Threshold tooltip says it applies to UI items.
I'm not sure what "2+Drag" is, but also in the keymap editor it is called Tweak, not Drag.
Hello Brecht, and thank you very much for your explanation.
Names in this form may in fact be misleading, because, as you can see in the picture below "Click Drag" may suggest a relationship with a "Drag Treashold" parameter.
Maybe "Click Tweak" in keymap would be a better idea?
Changed status from 'Archived' to: 'Open'
Ah wait, this is a new feature. Normally Tweak events are intended for this purpose.
@ideasman42, can we remove this
CLICK_DRAG
event? It's not used anymore in Blender code, tweak event handling is already complicated enough so would rather not have another similar way of doing it.Added subscriber: @pablovazquez
This was added to support keyboard shortcuts to be used for both pie menus and single key access.
For a while we had Tab-key access both pie menu and edit mode.
After testing we agreed this wasn't a good default because key-up events give the impression of lag, if you're not expecting it to behave this way.
But IIRC, from discussion at the time we thought this useful to be able to do, and people making their own keymaps customization could use it.
Without this there is no way to tell the difference between a click and a click-drag keyboard event:
This allows for some more flexible keymaps, OTOH, having click and click-drag on keyboard event's is not typically done.
@pablovazquez - what do you think? Is supporting different actions for tap/drag (typically pie menu) worth supporting?
EDIT posted on dev-talk: https://devtalk.blender.org/t/keyboard-tap-drag-dection-useful/5450
Even calling this tweak-threshold is misleading since it's used for click & double-click.
Having both is confusing, propose to use only one, see: D4322
Closing since this is more a UI/communication issue,
not a mistake in the code.
Changed status from 'Open' to: 'Archived'