Drecreased precision when adjusting input fields with Shift-Alt-Drag #45280

Closed
opened 2015-07-02 22:48:08 +02:00 by Thomas Radeke · 9 comments

System Information
Linux Mint 17.1 x64
nVidia GeForce GTX 770 using proprietary driver

Blender Version
Broken: 2.75
Worked: 2.74

Short description of error
When adjusting any input field using Shift+Alt+Drag, the minimum increment now seems to be at least one order of magnitude bigger than it used to be in 2.74. For some fields, like the object location, the precision seems to be the same as before, but some other fields have changed dramatically. (Also, the 3D cursor location fields are using a different precision than the object location fields.)
One instance where this is not only extremely noticable but also kinda breaks a feature for me is when trying to precisely adjust a background image, because the size field will now only work on two digits of precision, but it used to work on three digits in the last version.
This becomes even more extreme when working in metric units, because at scale 1.0 the minimum increment is now 10cm, which is completely unworkable. It used to work on 0.001 level, independently of the unit system.

Exact steps for others to reproduce the error

  • open Blender
  • add a background image to your scene
  • adjust the background image size with Shift+Alt+Left-Mouse-Dragging
  • notice the increment of 0.01 when using Blender units, 0.1 when using metric units.
**System Information** Linux Mint 17.1 x64 nVidia GeForce GTX 770 using proprietary driver **Blender Version** Broken: 2.75 Worked: 2.74 **Short description of error** When adjusting any input field using Shift+Alt+Drag, the minimum increment now seems to be at least one order of magnitude bigger than it used to be in 2.74. For some fields, like the object location, the precision seems to be the same as before, but some other fields have changed dramatically. (Also, the 3D cursor location fields are using a different precision than the object location fields.) One instance where this is not only extremely noticable but also kinda breaks a feature for me is when trying to precisely adjust a background image, because the size field will now only work on two digits of precision, but it used to work on three digits in the last version. This becomes even more extreme when working in metric units, because at scale 1.0 the minimum increment is now 10cm, which is completely unworkable. It used to work on 0.001 level, independently of the unit system. **Exact steps for others to reproduce the error** - open Blender - add a background image to your scene - adjust the background image size with Shift+Alt+Left-Mouse-Dragging - notice the increment of 0.01 when using Blender units, 0.1 when using metric units.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @ThomasRadeke

Added subscriber: @ThomasRadeke

#45281 was marked as duplicate of this issue

#45281 was marked as duplicate of this issue

Added subscriber: @mont29

Added subscriber: @mont29
Campbell Barton was assigned by Bastien Montagne 2015-07-03 09:09:16 +02:00

Campbell, iirc you removed that shift-alt-drag precision feature when you added "multi-edit" one?

Campbell, iirc you removed that shift-alt-drag precision feature when you added "multi-edit" one?
Member

Added subscriber: @DBrown

Added subscriber: @DBrown

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

This was an intentional change.

Using Alt+Shift no longer works for extra precise snapping.
Its in conflict with multi-value editing which can also use shift+drag for precise editing.

This was an intentional change. Using Alt+Shift no longer works for extra precise snapping. Its in conflict with multi-value editing which can also use shift+drag for precise editing.
Author

Thank you for clarifying.
I never had use for multi-value editing. However, ultra-precise snapping was an important part of my workflow and now that it's gone, I cannot adjust background images anymore.

Even if I might get ignored, I still want you to consider that this intentional change utterly destroys the ability to work precisely with metric units. Remember, the smallest possible increment is now 10cm. Besides, this change has introduced inconsistencies in precision handling, depending on the unit system. Adjusting numbers using Blender units is now 10x more precise than using metric units. :-(

Instead of just whining around, here's a suggestion:
Can't this feature be restored by making it assignable to a custom key combination?

Thank you for clarifying. I never had use for multi-value editing. However, ultra-precise snapping was an important part of my workflow and now that it's gone, I cannot adjust background images anymore. Even if I might get ignored, I still want you to consider that this intentional change *utterly destroys* the ability to work precisely with metric units. Remember, the smallest possible increment is now 10cm. Besides, this change has introduced inconsistencies in precision handling, depending on the unit system. Adjusting numbers using Blender units is now 10x more precise than using metric units. :-( Instead of just whining around, here's a suggestion: Can't this feature be restored by making it assignable to a custom key combination?
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
5 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#45280
No description provided.