Measure Tool Undo crash #116734
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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#116734
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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: Linux-6.6.8-200.fc39.x86_64-x86_64-with-glibc2.38 64 Bits, X11 UI
Graphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 545.29.06
Blender Version
Broken: version: 4.1.0 Alpha, branch: main, commit date: 2024-01-01 12:59, hash:
98c6bded9844
Worked: 3.6.7
Caused by
ebb5643e59
Short description of error
Measure Tool Undo crash
Exact steps for others to reproduce the error
from the default startup cube:
Measure
toolCaused by
ebb5643e59
CC @mont29
I think that the problem is in the ruler code...
view3d_ruler_to_gpencil
can be called fromgizmo_ruler_exit
, which (as far as I can follow code and guess) seems to happen after the undo step is saved?In any case, PR !116751 seems to fix the problem?
Think @ideasman42 or @mano-wii should be summoned here :)
I am not very familiar with this part of the code, but what I noticed is that "VIEW3D_OT_ruler_add" (which has the
OPTYPE_UNDO
flag) invokes "GIZMOGROUP_OT_gizmo_tweak", which is modal and does not have theOPTYPE_UNDO
flag. So, indeed, it seems the undo step is being added at the wrong moment.Maybe it could be a good idea to remove the
OPTYPE_UNDO
from "VIEW3D_OT_ruler_add" and explicitly callED_undo_push
within `gizmo_ruler_exit"?(Or maybe make more complex core changes and postpone the undo step if one operator calls another...)
@mano-wii AFAIK operators that are launched from other operators will never create an automatic undo step when they exit (this is ensured by the WM operators management code).
But I have no idea what's expected to happen (or what actually happens) when the first-level operator exits after invoking a second-level modal operator that keeps running... Maybe @ideasman42 or @JulianEisel know more about that?