Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
I'm doing my first steps in NT programming now and I'm already in trouble. Its strange but it seems like the changes I make in the script editor are ignored sometimes. So when I edit a line of code that was responsible for a compile error the same compile error remains even when the error is corrected or the line was deleted completely. I click the save button several times but without effect ... what am I missing here?
Kennt ihr den Moment, in dem plötzlich alles Sinn ergibt und man merkt, dass der ganze Scheiß sich wirklich lohnt? Ich auch nicht!
Can you help answer these questions from other members on NexusFi?
Well, without knowing something about the errors, it's not really possible to answer the question.
I will say that the compiler is not really ignoring the code changes. Probably there is an error further up in the code that is the real issue, and when the compiler flags a particular line, and then you change or delete that line, the real issue has not gone away.
Compiler errors are errors of syntax (wrong usage), or code structure, or something not having the right number or type of parameters, or something not being defined in the current scope context, etc. -- something formal. So, while a particular line may be flagged where the error takes place, you have to look at what is incorrect, or incomplete, or missing that is causing it.
Unfortunately, learning the knack of this probably will involve a certain amount of time, experience, and yelling at the computer while pounding on the desk....
Besides getting familiar with Ninja, you will need to be very familiar with C#, the actual language you are using. Sometimes, you will also need to understand at least some of the .NET framework to bring in additional functionality.
If you are already up on all this, I apologize -- I don't mean to talk down to you, in any case. But most of successful coding comes from doing it, and making mistakes until you have learned from them. There is a lot you can learn from reading existing code that works -- for example, indicators that do things that are similar to what you are doing. Or programming resources on the web.
But at least I can tell you not to think it's the compiler: look for a mistake that the line in question is actually a part of, and when that is fixed, the line will work also. (Assuming the changed line isn't still making the same error ....)
Good luck to you. All programming errors can be found and fixed. Sometimes it takes longer than other times. I hope it is fairly painless for you.
....)