Modal Operator Breaks on Workspace Change #77419

New Issue

Wayde Moss · 2020-06-05T08:34:13+02:00

Wayde Moss commented

2020-06-05 08:34:13 +02:00

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66

Blender Version
Broken: version: 2.83.0, branch: master, commit date: 2020-06-03 14:38, hash: 211b6c29f7
Broken: 2.82.7
Broken: 2.81.16

Worked: 2.79b

Short description of error
Modal Operators appear to break when changing work spaces or fullscreening a window space.

Exact steps for others to reproduce the error
Open attached file
Run script (OperatorModalDraw.py)
In view3D run operator
Either change workspace or RClick the header to maximize the view3D.
Drawing broken and a console error is thrown persistently: "internal error: modal gizmo-map handler has invalid area". This message is only shown for 2.83.

bug_op_modal_fullscreen.mp4

Blend file: modal_op_fullscreen.blend
It's an empty scene. The script used is the template Operator Modal Draw with a few minor changes to allow events to pass through and to not end on L/RClick.

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66 **Blender Version** Broken: version: 2.83.0, branch: master, commit date: 2020-06-03 14:38, hash: `211b6c29f7` Broken: 2.82.7 Broken: 2.81.16 Worked: 2.79b **Short description of error** Modal Operators appear to break when changing work spaces or fullscreening a window space. **Exact steps for others to reproduce the error** Open attached file Run script (OperatorModalDraw.py) In view3D run operator Either change workspace or RClick the header to maximize the view3D. Drawing broken and a console error is thrown persistently: "internal error: modal gizmo-map handler has invalid area". This message is only shown for 2.83. [bug_op_modal_fullscreen.mp4](https://archive.blender.org/developer/F8578338/bug_op_modal_fullscreen.mp4) Blend file: [modal_op_fullscreen.blend](https://archive.blender.org/developer/F8578325/modal_op_fullscreen.blend) It's an empty scene. The script used is the template Operator Modal Draw with a few minor changes to allow events to pass through and to not end on L/RClick.

Wayde Moss commented

2020-06-05 08:34:13 +02:00

Added subscriber: @wbmoss_dev

Germano Cavalcante commented

2020-06-08 15:08:29 +02:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2020-06-08 15:08:29 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Germano Cavalcante commented

2020-06-08 15:08:29 +02:00

I can confirm.
Theoretically the area should be the same.
And even if it were not, when returning to the previous layout, context.area should return to the previous state.

Besides, this is how it worked in blender 2.79.
So confirming as a bug.

I can confirm. Theoretically the area should be the same. And even if it were not, when returning to the previous layout, `context.area` should return to the previous state. Besides, this is how it worked in blender 2.79. So confirming as a bug.

Chris Kohl commented

2020-07-12 11:13:42 +02:00

Added subscriber: @ckohl_art

Ryan Southall commented

2020-10-21 18:32:59 +02:00

Added subscriber: @RyanSouthall

Vilem Duha commented

2021-01-14 12:44:04 +01:00

Added subscriber: @VilemDuha

Vilem Duha commented

2021-01-14 12:44:04 +01:00

Just few small notes , since I was also fighting this problem a lot -

regarding to the pythong Gotcha's docs it's not recommended to keep reference to 'any' blender data during modal operation, so this probably also includes context:
https://docs.blender.org/api/current/info_gotcha.html
It's better to implement a function that searches the best fitting/similar area to move the operator there, and if it isn't found, then end the operator.

context.copy() can fail in case some addons add properties or functions to it (like the X Muscle as far as I remember)

Just few small notes , since I was also fighting this problem a lot - - regarding to the pythong Gotcha's docs it's not recommended to keep reference to 'any' blender data during modal operation, so this probably also includes context: https://docs.blender.org/api/current/info_gotcha.html - It's better to implement a function that searches the best fitting/similar area to move the operator there, and if it isn't found, then end the operator. context.copy() can fail in case some addons add properties or functions to it (like the X Muscle as far as I remember)

Christian Brinkmann commented

2021-06-20 01:11:53 +02:00

Added subscriber: @p2or

Oleg commented

2022-04-19 21:48:33 +02:00

Added subscriber: @DotBow

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Modal Operator Breaks on Workspace Change #77419