Waxpatch on the demo

Question One

The demo provided in the Https://github.com/mmin18/WaxPatch URL can be run, but there is a problem if you change the patch.zip to your own and upload it to your own server (github), In the demo, replace the server address with the address of your patch.zip, and then debug, you will find the failure. The main reason for the failure is that the LUA interpreter cannot find Patch.lua and Mainviewcontroller.lua because the demo comes with an extract class that extracts our own patch.zip and creates a new directory patch in the extracted directory. Then extract the content into the directory. The normal situation is that the extracted directory should be Dir.../lua/patch.lua, but the directory extracted with its own patch.zip is Dir.../lua/patch/patch.lua, so the LUA interpreter does not find a Patch.lua error. Solution Solutions There is a "%@/" in the code. Lua;%@/?/init.lua;" Tells the LUA compiler where to load the LUA files to be compiled, so you can add patches here, and change them to "%@/patch/?". Lua;%@/?/init.lua;" You can write the Patch.lua in Dir.../lua/patch/patch.lua to Dir.../lua/patch.lua in your own code. Replace a set of decompressed class libraries

Question Two

Sometimes the above problem is solved or there is no such error, and the LUA interpreter package encounters an unrecognized character in a. lua file when it is compiled, because a third-party input method may be used in the Mac to cause Solution Solutions When you edit LUA files with Lua-specific editors, you can use sublime Text2 and so on, and such editors can see the wrong full-width characters, which can then be modified.

Waxpatch on the demo