Measuring Tool doesn't snap with CTRL #66554

Closed
opened 2019-07-08 14:51:37 +02:00 by Bradley M Small · 14 comments

System Information
Operating system: Linux-4.9.0-9-amd64-x86_64-with-debian-9.9 64 Bits
Graphics card: GeForce GT 555M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-07 20:28, hash: d19d0ff99e
Worked: (optional)

Short description of error
Measuring tool does not snap when ctrl-key is held down.

Exact steps for others to reproduce the error
Draw line with the measuring tool, then grab an end and drag it to the corner of the cube and hold down CTRL in the hopes that it will snap to the corner and it doesn't.

**System Information** Operating system: Linux-4.9.0-9-amd64-x86_64-with-debian-9.9 64 Bits Graphics card: GeForce GT 555M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116 **Blender Version** Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-07 20:28, hash: `d19d0ff99e` Worked: (optional) **Short description of error** Measuring tool does not snap when ctrl-key is held down. **Exact steps for others to reproduce the error** Draw line with the measuring tool, then grab an end and drag it to the corner of the cube and hold down CTRL in the hopes that it will snap to the corner and it doesn't.

Added subscriber: @Absinthe

Added subscriber: @Absinthe

This issue was referenced by a4bc6aca0e

This issue was referenced by a4bc6aca0ef96ce5e4b011cd33477e551269fa1e

Added subscriber: @mano-wii

Added subscriber: @mano-wii

It is working fine here. Did you change the default keymaps?
Try with the default Blender settings (File -> Defaults -> Load Factory Settings).

It is working fine here. Did you change the default keymaps? Try with the default Blender settings (`File -> Defaults -> Load Factory Settings`).

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Campbell Barton self-assigned this 2019-07-08 16:19:13 +02:00

That didn't seem to change anything. It does work on my other machine, but not on this one. The Shift seems to work for what it does. But the Ctrl is not causing snapping, only bullseye highlighting after release.

That didn't seem to change anything. It does work on my other machine, but not on this one. The Shift seems to work for what it does. But the Ctrl is not causing snapping, only bullseye highlighting after release.

Changed status from 'Resolved' to: 'Open'

Changed status from 'Resolved' to: 'Open'

@Absinthe, reopening - we will need a test case to reproduce the error.

@Absinthe, reopening - we will need a test case to reproduce the error.

Not that the issue fixed is pressing Ctrl on it's own didn't refresh snap (you needed to move the cursor after to refresh snapping).

Not that the issue fixed is pressing Ctrl on it's own didn't refresh snap (you needed to move the cursor after to refresh snapping).

I just tried it at work on yet a different machine and again it works exactly as expected here too.

When I do other snapping actions there is a reasonably responsive snapping response. I would only assume that this would behave with some similarity to them as it does on the other machines upon which it does work.

When it fails it is simply starting the program, clearing the popup screen, selecting the tool and drawing an arbitrary line followed by grabbing one of the ends and dragging it to the corner of the default cube. With the ctrl held (where it doesn't work) there is no snappiness or jumpiness to the point. As a matter of fact once placing and releasing the end rotating the screen shows that it is nowhere near the snapping area as it is out of plane with any line or vertex even remotely near where you would have thought you were trying to place it.

I just tried it at work on yet a different machine and again it works exactly as expected here too. When I do other snapping actions there is a reasonably responsive snapping response. I would only assume that this would behave with some similarity to them as it does on the other machines upon which it does work. When it fails it is simply starting the program, clearing the popup screen, selecting the tool and drawing an arbitrary line followed by grabbing one of the ends and dragging it to the corner of the default cube. With the ctrl held (where it doesn't work) there is no snappiness or jumpiness to the point. As a matter of fact once placing and releasing the end rotating the screen shows that it is nowhere near the snapping area as it is out of plane with any line or vertex even remotely near where you would have thought you were trying to place it.

I found out what went wrong. This is a matter of having the setting of "pointer location" in the TweakUI tool | Keyboard & Mouse set to on. Once I set that off the problem goes away and things snap with the Ctrl key as I expect. This is not an uncommon setting to help find your mouse pointer. However, I would be satisfied just knowing that it was not a compatible setting.

I found out what went wrong. This is a matter of having the setting of "pointer location" in the TweakUI tool | Keyboard & Mouse set to on. Once I set that off the problem goes away and things snap with the Ctrl key as I expect. This is not an uncommon setting to help find your mouse pointer. However, I would be satisfied just knowing that it was not a compatible setting.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

Warning when there are conflicts in the keymap would be a good feature.
But currently some operators work with the same keymap but in different contexts or with the same context but with PASS_THOUGH allowing more than one operator to run with the same command.
So it would not be something simple to implement.

Warning when there are conflicts in the keymap would be a good feature. But currently some operators work with the same keymap but in different contexts or with the same context but with `PASS_THOUGH` allowing more than one operator to run with the same command. So it would not be something simple to implement.

Changed status from 'Archived' to: 'Archived'

Changed status from 'Archived' to: 'Archived'
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
4 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#66554
No description provided.