Code Under Construction

[Zeos6]

Hi,

I have run into the following situation and was wondering if there is some way around it. Your suggestions would be greatly appreciated. Thank you.

I am building an indicator X. It is a fairly complex piece of code and I am working on it bit at a time. The code is incomplete and consequently has errors - it would be impractical to remove all the code causing the errors. I have found that I cannnot import any new indicators or compile other indicators built until all the errors in X are resolved. This is quite anoying. I literally have to copy the code into a Word file, delete the indicator X from Ninja, do what I need with the other indicators and then rebuild X.

Is there a cleaner way for me to compile other completed indicators, or import new indicaotrs while still having code for X with errors? Also, can anyone explain to me why Ninjatrader is built this way? Seems very restrictive. I am not trying to use X on my charts yet; I am just compliling it and debugging by eliminating errors.

[NinjaTrader_RyanM1]

Hi Zeos6,

I would work with the file location. If you move it outside of \bin then it won't be included when you compile.

NinjaTrader was designed this way to ensure integrity of the codebase before running your script. You'll see this in other development environments as well. You're not able to run a vb program if it has compile errors.

[Zeos6]

Hi Ryan,

Thank you. That will help a lot. Re the integrity of the codebase, I understand. If this was specific to the individual indicator and not the entire library of indicators it would make more sense to me. Say I have 10 indicators and all of them compile correctly and work properly. Say I export one of those indicators and delete it from the library. Now I add one indicator that does not compile. Why should I not be able to import the initial correct indicator exported , one that I know works properly into the indicator library?

In any case, this has helped a lot Ryan. Thank you.

[NinjaTrader_RyanM1]

Glad that work-around will work for you.

The import process runs a check against all files to make sure they're in a compilable state. This is really to help isolate the cause of potential programming errors. You don't want to incorrectly attribute programming errors to a new script when they were already there before importing.

If you absolutely need to import before resolving errors, you can manually place files where they need to go and add any references, but we are not able to provide support for this approach.

[Zeos6]

Hi Ryan,

Understood. Thank you for your help. This has already helped a lot.