if this condition if(TrailingStop>0) IS TRUE - in such a case following lines will be executed, otherwise not - does your trading meet this requirement? or didn't you change TrailingStop (input parameter) to make checking this condition to give TRUE ... Think logically!...
if((OrderOpenPrice()+ (BEStopPips*MyPoint))>Bid) ...- perhaps additional brackets can help...
perhaps in your MT-build some functions are called differently... nobody has the same trading & soft environment as you, but logically the code seems to be correct at a glance
if this condition if(TrailingStop>0) IS TRUE - in such a case following lines will be executed, otherwise not - does your trading meet this requirement? or didn't you change TrailingStop (input parameter) to make checking this condition to give TRUE ... Think logically!...
if((OrderOpenPrice()+ (BEStopPips*MyPoint))>Bid) ...- perhaps additional brackets can help...
perhaps in your MT-build some functions are called differently... nobody has the same trading & soft environment as you, but logically the code seems to be correct at a glance
I didn't understand if you've got what you wanted ?...
but the only possible reason for violation in the calculation itself, I can assume, IS double behavior in calculations (testing needed) - some knowledge or even tricks (CompareDoubles) needed sometimes... the overall logics is normal in the code as I mentioned above...
(as well as you have double OpenPrice & int BEStopPips)
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.
thank you , but I am not a coder :((:((
but you can read, not coding :
if this condition if(TrailingStop>0) IS TRUE - in such a case following lines will be executed, otherwise not - does your trading meet this requirement? or didn't you change TrailingStop (input parameter) to make checking this condition to give TRUE ... Think logically!...
if((OrderOpenPrice()+ (BEStopPips*MyPoint))>Bid) ...- perhaps additional brackets can help...
perhaps in your MT-build some functions are called differently... nobody has the same trading & soft environment as you, but logically the code seems to be correct at a glance
but you can read, not coding :
if this condition if(TrailingStop>0) IS TRUE - in such a case following lines will be executed, otherwise not - does your trading meet this requirement? or didn't you change TrailingStop (input parameter) to make checking this condition to give TRUE ... Think logically!...
if((OrderOpenPrice()+ (BEStopPips*MyPoint))>Bid) ...- perhaps additional brackets can help...
perhaps in your MT-build some functions are called differently... nobody has the same trading & soft environment as you, but logically the code seems to be correct at a glance
thank you
thank you
I didn't understand if you've got what you wanted ?...
but the only possible reason for violation in the calculation itself, I can assume, IS double behavior in calculations (testing needed) - some knowledge or even tricks (CompareDoubles) needed sometimes... the overall logics is normal in the code as I mentioned above...
(as well as you have double OpenPrice & int BEStopPips)