Info: Registering menu class: 'ALL_MT_editormenu', bl_idname 'ALL_MT_editormenu' has been registered before, unregistering previous

[Draise14]

Console issue spanning from our ALL_MT_editormenu system. Might be new warning code in there and we had it wrong a while.

[Draise14]

I think it is because every document is registering the same class 15 times more in 15 additional documents. They must have added a new checker system, or maybe we can reference the same class from somewhere common and remove the multiple registries from other documents?

[Draise14]

Did a quick test, removed one of the registries in a document, it removed the warning - no broken changes.

[ReinerBforartists]

Be careful with this one. I once needed to add the class to every editor to get it working. It is the show hide editor type menu

[Draise14]

The clip editor I tested on appeard to continue to work, so will.. branch and test before merging to master if I do manage a fix.

[ReinerBforartists]

This is what happens when you remove the class from one file. I did this here in the console editor.

Well, it worked for eight years or so to have the same class in the different files. Long enough i guess. Interesting would be to know the commit that made our previous working method uselsess. But we need a solution.

What we can do is to make every class unique now. The one for the console becomes then ALL_MT_editormenu_console, the one from the 3d view ALL_MT_editormenu_3dview, and so on. Then the error should vanish.

[Blenux]

Changes were made here, has above best to just add a editor suffix in each own file.

116374

116370

[ReinerBforartists]

So when two addon developers chooses the same class name the console will be spammed with error messages now, and slow down Blender? This change is crazy ...