Internal error after switching the viewport to max area.

[capnm]

System Information

• OS: Linux
• Blender version: 2.83.2, 2.9 alpha
• Add-on version: 519e04c

Description about the bug
After switching the viewport to max area [Ctrl + Space]
the Blender terminal output is spammed (until you disable the plugin) with

internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
internal error: modal gizmo-map handler has invalid area
...

Doesn't happen if the addon is deacticated.

Screenshots/Files [Optional]

[nutti]

@capnm

I could not reproduce this error.
I think this error message from Blender Internal Window System.

I found similar issue is raised in some other add-on, but I think we could not fix this from add-on level.
https://developer.blender.org/T66256

I think this does not have any serious problem judged from below comments.
https://github.com/blender/blender/blob/2d1cce8331f3ecdfb8cb0c651e111ffac5dc7153/source/blender/windowmanager/gizmo/intern/wm_gizmo_map.c#L977-L979

For now, I will close this issue due to the problem of Blender itself and the impacts to the main feature.
After this issue is fixed described in D.B.O, this error seems to be disappeared.

[capnm]

This seems to me to be relatively serious, it begins to print the line in a tight loop (~ 100% CPU load) until I stop the add-on. I found the same issue with jayanam/shortcut_VUr#24

[nutti]

@capnm

Understood.
But we can avoid this issue if we restart Screencast-Key or not to launch Blender from console.
So, I said this issue is not serious.

Anyway, we could not handle this issue from add-on level as I said before.
I think the best way to solve this issue is contacting the Blender developer.
https://developer.blender.org/T66256
Or, if you can build Blender from sources, you can delete the codes not to output these logs.

I think other add-ons which uses model operator such as jayanam/shortcut_VUr#24 raises this issue.

[capnm]

Thank you for the hints! I mentioned the issue in the upstream bug report. I've found other bad side effects as well, but I can use a screencast key tool for the operating system as a workaround, so in the end it isn't a serious problem for me ;-)

[machin3io]

You can avoid this by switching the workspace back and forth. Not pretty, but at least it avoids the terminal spam:

current = context.workspace
other = [ws for ws in bpy.data.workspaces if ws != current]

if other:
    bpy.context.window.workspace = other[0]
    bpy.context.window.workspace = current

Can be done in the the op's invoke().