WM_OT_context warnings in the console

Reiner's picture
Project: 
Bforartists Tracker

Seems that one of our changes has introduced a bug. I have a pretty while several WM_OT_context messages in the console. Which appears when i am with the mouse over some UI elements, and the tooltip comes up.

Per action and upcoming tooltip this one gets added then:

        WM_OT_context_toggle
        WM_OT_context_toggle_enum
        WM_OT_context_cycle_int
        WM_OT_context_cycle_enum
        WM_OT_context_cycle_array
        WM_OT_context_menu_enum

 I had once the message of a missing menu. But forgot to make a screenshot then. But i did copy the error message.

I have no idea if this is even connected. Fingers crossed that it's not two bugs ...

search for unknown menutype INFO_MT_mesh_add
uiItemM: not found INFO_MT_mesh_add

H:\bforartists\bforartists_build64\bin\Release\2.76\scripts\startup\bl_ui\space_
view3d.py:1048
search for unknown menutype INFO_MT_curve_add
uiItemM: not found INFO_MT_curve_add

H:\bforartists\bforartists_build64\bin\Release\2.76\scripts\startup\bl_ui\space_
view3d.py:1049

 

 

 

Status: 
Closed (fixed)
Priority: 
Normal
Category: 
Task
Component: 
User interface
Assigned: 
Images: 
Reporter: 
Created: 
Sat, 11/28/2015 - 11:57
Updated: 
Sun, 12/06/2015 - 11:49

Comments

10
Reiner's picture

Assigned: Unassigned » Reiner
Reiner's picture

Okay, two independant bugs. The issue with the missing menus doesn't belong here. I was a bit too fast with deleting the one or another class in the python ui files. To be precise, in the space_view3d.py

This bug with flooding the console with WM_OT messages also happens in Blender 2.76b. So it's one of the Blender 2.76a or b patches that caused this. Needs a bug report for Blender ...

Reiner's picture

Not to find in the Blender Bug Tracker by simple searching. Seems that i have no other choice than to try out all bugfixes that gots created since the release of Blender 2.76b. Or to revert all 2.76a patches that i have applied at Bforartists. And have a look at what point the problem vanishes.

But this is something too big for now. Will tackle this issue when i am through with the keymap branch.

Postponed.

Reiner's picture

Status: Active » Postponed
Reiner's picture

Assigned: Reiner » Unassigned
Reiner's picture

Assigned: Unassigned » Reiner

Okay, Keymap is done. So next try to get rid of this rascal. This time by reverting the Blender 2.76a patches. Blender 2.76 worked fine. Bforartists 0.2 worked fine. Blender 2.76a already showed this problem. So it's one of those patches.

Reiner's picture

Status: Postponed » Active
Reiner's picture

This one seems to be the baddie:

  • 3751eb1: Fix broken comment about our WM progress report for python (its not a progress bar at all).

Now let's have a look how to fix this one.

Reiner's picture

Yep, that was it. It was as simple as commenting out the printf statement, which was commented out before this patch.

Fixed in master

https://github.com/Bforartists/Bforartists/commit/f3047bf4ff38b5a27361f4...

Reiner's picture

Status: Active » Closed (fixed)