Incorrect behaviour of Snap Utilities Line Addon #80481
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
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-addons#80481
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?
version: 2.91.0 Alpha, branch: master, commit date: 2020-09-03 20:57, hash: a96283ba511d, type: Release
build date: 2020-09-03, 23:18:14
platform: Linux
System info: system-info.txt
Erroneous mouse behavior when using the Snap Utilites Line addon. The mouse position does not seem to correspond to the position inferred and used by the addon, as shown in the following video. Moreover, the dot that indicates the current mouse position seems to be lagging compared to the true mouse position in the viewport.
2020-09-04_21-39-05_edit.mkv
Added subscriber: @MeiKasahara
Added subscriber: @mano-wii
Changed status from 'Needs Triage' to: 'Confirmed'
I can confirm.
The problem is caused by mixing python drawing APIs.
I'll take a better look at this next week
This particular issue with the behavior of that tool appears to be fixed in Blender version: 2.91.0 Alpha, branch: master, commit date: 2020-10-11 22:38, hash: df3d124e9104.
Changed status from 'Confirmed' to: 'Resolved'
This issue was referenced by blender/blender@ed817d62bd
This issue was referenced by blender/blender@4430e8a008