@kestra I answered your previous thread. Please focus on that one and don't duplucate them.

@jstap Of course! XD

@ambrogio Yea, i figured that 0.01 will not work for some assets because of varieties of broker's tick size ... so I had to fetch the data out and adjust to the accurate round numbers but it's looking like the not so correct ones is doing the job better

Still checking though

Thanks

@TipsyWisdom When backtesting on M1 bar data, the ticks generated to build that candle are interpolated. That means, there are ticks that make up the OHLC of the candle, but everything in between is made up of random ticks that travel somewhat up and down.

Therefore, let's assume a candle has a high and low wick. Has it reached the high first before the close, or the low? This question is the key and holds a critical answer, at which most scalpers will be given false hopes that their system will yield real results after the backtesting looks good.

The only real way to test your strategy properly is forward testing, on a demo account. This will be very accurate and will be as close to live trading results as you're likely to get

To round off just in case the good work of the previous ones, if we want to activate it it's the same but adding the '!' to the conditional:

<<Global variables>>
#include <WinAPI/winapi.mqh>
#include <WinAPI/winuser.mqh>
#define MT_WMCMD_EXPERTS 32851
#define WM_COMMAND 0x0111
#define GA_ROOT 2

<<Settings>>
if (!TerminalInfoInteger(TERMINAL_TRADE_ALLOWED)){

HANDLE hchart = ChartGetInteger(ChartID(), CHART_WINDOW_HANDLE); HANDLE hmt = GetAncestor(hchart, GA_ROOT); PostMessageW(hmt, WM_COMMAND, MT_WMCMD_EXPERTS, 0);

}

@jstap

The performance of the EA works like prince charming when ran on a SINGLE chart. On ANY single chart it's fine.

When it's dropped on more than one orders DO NOT open correctly.

That's all I'm trying to express fella.

Yes to separate the types of trades the blocks are working with

It will never be empty. The variable will always have a value in it. And yes, that block will automatically change the value of the variable overwriting it on top of the previous one.

@iPod
Thanks for the tip.
I noticed that too.
After I deactivated 4 threads, it was about 3.2 GB per thread.