@hfcandrew : I didn't try ToolManager on P3 yet. Simple reason. I compiled the code to a standalone application (in P2) which ships all stuff inside (e.g. this runs on a machine where neither Python nor mmApi is installed) and performance seems to be better. BTW: Can't you simply keep Python2 along with Python3 on WIN and run the ToolManager from P2 ? This isn't a problem on macOS here.
Porting ToolManager to P3 needs to be done for Toolbox reasons and is the next point on my ToDo list.
mmappi.py is automatically generated by SWIG and this is OS specific. So my file most likely isn't much help on WIN. Also the SWIG stuff seems to work on your side. Otherwise you would get tons of errors....
I attach my mm folder. I transferred the original mm codes using 2to3 . But most of it are just wrapped SWIG calls- same for P2 and P3 there's not that much difference. Besides the 2to3 auto conversion I needed to modify
def get_object_name in scene.py (there are comments at the lines I edited).
Maybe there's a function used in ToolManager which I never used for other codes on P3? As said I'll look into it....
