Any rookie question, so as not to clutter up the forum. Professionals, don't pass by. Nowhere without you - 6. - page 747
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
2) There cannot be UPPER and LOWER fractals on the same bar at the same time, respectively, check
belongs to the category of programmer idiocy.
Both fractals can be on the same bar
he meant minutes, but forgot about months
What's the difference between minutes and months?
What is it complaining about in the modification log? "Stupidly opens new pending orders" because there is no limit, but there is an OrderSend.
What's the difference between minutes and months?
1) Any strategy must be defined by the number of orders open at the same time. Accordingly, before opening the next order, we should check how many are already open.
2) On one bar, there cannot be UPPER and LOWER fractals at the same time, respectively, the check is classified as
belongs to the category of programmer's idiocy.
3) Before writing the conditions for returning buffer indicator values, you need to know exactly what value is "empty" for it? Have you checked that it is 0?
4) The construct.
Although it will work (in most cases), but is unnatural, because it is a "free-will" idea of the developer, and is uninformative for the trader. An alternative - the tracking of a new bar.
5) You have to start from the basics, because this:
Indicates that you don't understand what you're writing at all.
The best way to understand is to study how other people's codes work and modify them for your own purposes. Good luck.
And this code
it is better to write in init() and better not like this
and then in start()
tp = High[3]+TP*point;
And this code
it is better to write in init() and better not like this
and then in start()