|
Developing new API functionality
|
Previous Top Next |
There is literally no reason to develop directly inside the API unless you are modifying existing features. Developing inside the API is only going to confuse you and make your life more difficult. For example, developing directly in the API you must unload MQ2 completely and reload before continuing a test. Instead, do your developing in a plugin. The code can then be copied directly and with very little modification into the API if necessary. Plugins can always be unloaded and reloaded on the fly without taking extra steps of shutting down MQ2 completely. In this way you can also take advantage of the MQ2 framerate limiter while developing, and not have to sit around or close EQ while your work compiles.