Reverse Engineering Problems

I have used the reverse engineering tool ax4.0 some time ago. I have no problem, but I am still confused today. Instead, I have generated a Visio file, but there is no content. Tracked CodeAx stores the reflected data in a temporary file, then, import the temporary file to the Visio file through an add-on named UML background add-on of the Visio COM object. The imported action occurs in the class
In the run-> loadimportfile method of sysvisionaddin
Addon. Run (strfmt (# addoncommand, documentindex, winapi: getdomainpathname (importfile. parmimportfilename ())));
This line of code imports the code to the currently created Visio file, which is the same as the macro command in Visio to import the file, but this path is not clear and does not support Chinese, this command cannot be executed as long as the path contains Chinese characters.
If you are not familiar with this problem, you cannot change it to support the Chinese path. The temporary solution is: generate a Visio file and do not store it in a path containing Chinese characters, for example, a path containing a desktop.

In addition, visio2007 cannot be exported successfully because the getumladdon method called by loadimportfile traverses all the add-on methods in current Visio, find the response with the name "UML background add-ond" and obtain the name of add-on using addon. name (), which is no problem under visio2003, but under viso2007, this method returns Chinese, when compared with "UML background add-ond", the corresponding add-on cannot be found.
Ax5.0 has fixed this bug and obtained the addon name through addon. nameu (). The problem is that there is no comparison in English.

To sum up:
1. The export path of Visio cannot contain Chinese characters;
2. If visio2007 is used, change addon. Name () of the getumladdon method of sysvisioaddin to addon. nameu ().