You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Peter, so we create the trailing code in the script? Great! What you have listed I now take as basic sections and start to describe them in words, so that it is clear how to write functions, loops, etc. later. Is this correct?
Regards, Vladimir.
You cannot use any script for trailing. It undermines the very idea of what I am trying to tell you.
Got it, Vassili! I put everything on hold then.
Regards, Vladimir.
You can't use any script for trailing. It undermines the very idea of what I am trying to tell you.
Got it, Vassili! I'll put everything on hold then.
Respectfully, Vladimir.
There is no fundamental difference where to write trailing functions, the main thing is to write and learn.
You cannot call OnTick in the script)
Got it, Vassili! I'll put everything on hold then.
Respectfully, Vladimir.
You cannot call OnTick in the script)
There's an observation that once you start crunching, it's hard to stop, and as a consequence, the project code turns into what's known as d.c.
Let me explain:
I hope you paid attention to the fact, that the counter of implemented features, increases time of implementation of the next feature, but when implemented correctly, it resets to zero?
This is a very exaggerated idea, but that's how it works in real life.
What I mean is if you don't rewrite the project after you implement all the features it will go into production as an unreadable spoiler. And then, the life cycle of any project leads to a headache for the management: either to put the entire team on a global refactoring of all the things they have spun (and the competitors don't sleep, they, evil guys, write new features), or keep writing crutches and patching bugs, leaking in torrents.
Regulation and regulation again. And for violations, excommunication)))) and in a monolithic procedure everything can be implemented too )))).
Although, ok, I agree, all the former can still be, but new workers in the rules is an extra cost).
And to be honest, of course, after having more than 3-5 different data sources and more than 3 different processing algorithms, global variables without a clear regulation of their declaration is evil.
At runtime, all computational variables are globally declared. After processing, you can wrap them in anything you like)
Regulation and regulation again. And for infringements, excommunication))))) and in a monolithic procedure everything can also be implemented))))
Although, I agree, all the former can still be done, but it is too expensive to put new employees into the procedure)
He wasn't going to. He would have blocked the flow of the script and in an eternal loop would have jerked the trading environment. That is to say, it would do it all at once in a brutal way.
This is what I imagined, but only with Sleep function in the script and possibility to set sleep period from 1 to 10 seconds.
Respectfully, Vladimir.