Posts made by roar

@l-andorrà Check your objects list. You create object named "Sells1", but later you check for "Sells" object.

The "1" is added because you tell the "Draw button" block that there will be many similar objects, so the "Sells" is just a prefix and a number will be added after it.

To fix, just set setting B = Yes

@Archer The time between the distance check and order send is minimal, milliseconds at most. The time for finalizing the order in the server takes 100x more time. You cant make the broker server faster with any extra condition. But if you cant allow 1 pip of slippage, I think you need to work with pending orders instead of market orders.

@MMBInvest DoubleToString() always works, I dont know what else to say. Here is an example you can actually reproduce, maybe it helps.
testtt.mq4

@Archer if the EA seems to not follow the 2 pip rule, dont add more rules but instead troubleshoot why the 1st rule is not followed. This can be done by simply printing out the values the EA looks at:
https://fxdreema.com/shared/1ihsjoy2d

@Archer pip values on JPY pairs can be messed up.
Try replacing the Pips with a _Point conversion

@Archer here's some example
https://fxdreema.com/shared/h6BiNKJoc

• You are calculating the lot size after the next trade is already opened, not sure if that makes sense
• To make an EA work together with manual trades, you need to filter by group "All"
• If you have a pre-defined list for each subsequent order size, you must always check the current count of trades and selecting the proper lot size according to the count, before making the next addition

@LightMasterSunrise youre in way over my head too, lol

If you have the mql5 code, I can surely help getting it to fxdreema format

Your indicator probably uses 0 as the default value (where nothing should be plotted). Good indicators use EMPTY_VALUE as the default. Try adding extra condition "indicator != 0" to your flow.

Your example seems to be working just fine

Its difficult to reproduce the bug with this, even when making it backtestable: https://fxdreema.com/shared/hPqJMbjyb

Can you find some number that produces the infinite zeroes with StringToDouble?

The example doesn't compile, but I assume the printProfit is a string variable

@MMBInvest it is a common issue with mql language itself, I think it would happen if you coded the whole thing in Metaeditor. https://www.forexfactory.com/thread/1190602-rounding-in-mql4

NormalizeDouble often fails to cut the digits, but DoubleToString does work for me 100%.
Can you show some example case in shared link?

@l-andorrà I just used them for troubleshooting, should have removed from the shared version

Put 1 to the Type field and any of 2 to the Value field

@DanZig55 I have used those 3 bullet points in many EAs.

On mql4 its actually a bit easier, because you can use iMAOnArray() without importing anything: https://docs.mql4.com/indicators/imaonarray

So it would be something like this
https://fxdreema.com/shared/TUPEbGVXd

https://www.mql5.com/en/code/77

You need to import this library (using a custom block), then you can call the LinearWeightedMA() function on your variable, assuming its an array.

25% drawdown on the 2nd day of trading, I think that tells all.

Anyway mad respect for disclosing the live performance.