Fox_RM: I've made a comparison. Found the mistakes. Thank you! Why is it still not correct? What else needs to be fixed and what do we need to work on?
The last variant seems to be working more or less. Although we could simplify the calculations
The FAQ says it right. You can't rely on "defaults". Because I remember that 131 error (wrong lot) often came up, if you don't do a normalization before sending an order. Maybe now the MMOs have done their own default lot checking on the servers when sending an order for execution.
So you should always do your own price and lot normalization before sending.
This is a good coding rule for you, and a guarantee of less hassle with potential problems in the future.
))Guys, thanks so much for wanting to help...it's finally working for me here
Guys, Help please, I am writing an EA in MLQ4. to break the HIGHT of a past candle (M15 timeframe) if this candle closed below the opening price,
(If a new candlestick breaks the previous HIGHT, the robot would open a BUY order with the TP and SL set)
The robot should also check for any open orders and not open new ones, if there are already open deals. The criterion for order closing would be TP or SL, which was set by the user.
Guys, Help please, I am writing an EA in MLQ4. to break the HIGHT of a past candle (M15 timeframe) if this candle closed below the opening price,
(If a new candlestick breaks the previous HIGHT, the robot would open a BUY order with the TP and SL set)
The robot should also check for any open orders and not open new ones, if there are already open deals. The criterion for order closing would be TP or SL, which was set by the user.
Guys, Help please, I am writing an EA in MLQ4. to break the HIGHT of a past candle (M15 timeframe) if this candle closed below the opening price,
(If a new candlestick breaks the previous HIGHT, the robot would open a BUY order with the TP and SL set)
The robot should also check for any open orders and not open new ones, if there are already open deals. The criterion for order closing would be TP or SL, which was set by the user.
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
DigCode Base
If you can't find it, then order it.
Vinin:
Edited the indicator again
I've made a comparison. Found the mistakes. Thank you! Why is it still not correct? What else needs to be fixed and what do we need to work on?
The last variant seems to be working more or less. Although we could simplify the calculations
The FAQ says it right. You can't rely on "defaults". Because I remember that 131 error (wrong lot) often came up, if you don't do a normalization before sending an order.
Maybe now the MMOs have done their own default lot checking on the servers when sending an order for execution.
So you should always do your own price and lot normalization before sending.
This is a good coding rule for you, and a guarantee of less hassle with potential problems in the future.
Guys, Help please, I am writing an EA in MLQ4. to break the HIGHT of a past candle (M15 timeframe) if this candle closed below the opening price,
(If a new candlestick breaks the previous HIGHT, the robot would open a BUY order with the TP and SL set)
The robot should also check for any open orders and not open new ones, if there are already open deals. The criterion for order closing would be TP or SL, which was set by the user.Guys, Help please, I am writing an EA in MLQ4. to break the HIGHT of a past candle (M15 timeframe) if this candle closed below the opening price,
(If a new candlestick breaks the previous HIGHT, the robot would open a BUY order with the TP and SL set)
The robot should also check for any open orders and not open new ones, if there are already open deals. The criterion for order closing would be TP or SL, which was set by the user.This will help.
Guys, Help please, I am writing an EA in MLQ4. to break the HIGHT of a past candle (M15 timeframe) if this candle closed below the opening price,
(If a new candlestick breaks the previous HIGHT, the robot would open a BUY order with the TP and SL set)
The robot should also check for any open orders and not open new ones, if there are already open deals. The criterion for order closing would be TP or SL, which was set by the user.