Fractional step in value input for Skin Modifier (Event/input problem) #31584

Closed
opened 2012-05-24 10:47:29 +02:00 by Daniel Salazar · 5 comments
Member

%%%This one is weird.. It's about Ctrl + A for scaling "vertex size" in skin modifier

If you press Ctrl + A slowly it works smoothly as expected
If you press Ctrl + A in rapid succession a fractional step of .1 is given to the value input

This is probably not your code even but I'll assign to you so you can decide%%%

%%%This one is weird.. It's about Ctrl + A for scaling "vertex size" in skin modifier If you press Ctrl + A slowly it works smoothly as expected If you press Ctrl + A in rapid succession a fractional step of .1 is given to the value input This is probably not your code even but I'll assign to you so you can decide%%%
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'

%%%I have observed this as well. As far as I can tell it's not skin related (I've seen similar problems with modifier keys elsewhere in Blender too.)

Unassigning self, hopefully someone with more event-system knowledge can check.%%%

%%%I have observed this as well. As far as I can tell it's not skin related (I've seen similar problems with modifier keys elsewhere in Blender too.) Unassigning self, hopefully someone with more event-system knowledge can check.%%%

%%%Can confirm this has nothing related to modifier, it’s a problem with transform code.

To be precise, you can reproduce the bug by releasing the modifier key (ctrl here, but same problem would arise with shift…) before the A key. This is caused by a piece of code at init transform time (initTransform, transform.c, lines 1668-1686), which enables snapping if ctrl (or shift) key is pressed at init time.

This allows snapping to be on when you click on transform widget with ctrl key pressed… but also enables it when you start a transform tool with a shortcut using such modifier!

I guess things work OK when you release ctrl after A because this generates an event while the transformation is already active, and hence is correctly detected as a “snapping deactivation”.

Either way, we are hitting the limits of trying to manage/detect continuous states with discrete events (here ctrl key press/release). Maybe we should rather test those modifiers in all transformEvent calls, but I guess this would broke the shortcut system… :/%%%

%%%Can confirm this has nothing related to modifier, it’s a problem with transform code. To be precise, you can reproduce the bug by releasing the modifier key (ctrl here, but same problem would arise with shift…) *before* the A key. This is caused by a piece of code at init transform time (initTransform, transform.c, lines 1668-1686), which enables snapping if ctrl (or shift) key is pressed at init time. This allows snapping to be on when you click on transform widget with ctrl key pressed… but also enables it when you start a transform tool with a shortcut using such modifier! I guess things work OK when you release ctrl after A because this generates an event while the transformation is already active, and hence is correctly detected as a “snapping deactivation”. Either way, we are hitting the limits of trying to manage/detect continuous states with discrete events (here ctrl key press/release). Maybe we should rather test those modifiers in all transformEvent calls, but I guess this would broke the shortcut system… :/%%%

%%%Fixed in svn rev48864. Not ideal, but don't think it makes code more silly there.
Thanks for the report, closing.%%%

%%%Fixed in svn rev48864. Not ideal, but don't think it makes code more silly there. Thanks for the report, closing.%%%

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
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#31584
No description provided.