Problem regarding difference in MT4 - MT5 for accessing datetime in the future

#1

Hi, I converted the Battleplan indicator (found in the network) from MT4 to MT5 successfully, but I still have a problem.

The diffulty I enconter is to do the indicator in MT5 to paint the battleplan for future time date. In MT4 the indicator paint the battleplan even for future data, in MT5 if I try to do the same I get array out of range.

I attach both the MT4 code and MT5 code.

battleplan.mq5

battleplan_ciclo_4_tempi.mq4

I even tried to resize both array (time & Hurst) with an appropriate dimension but I get the same error

Here are the changes i tried in MT5 version but without success

//ArraySetAsSeries(time,true);

//ArraySetAsSeries(Hurst,true);

......

ArrayResize(Hurst,limit+(int)cyclelength);

ArrayResize(time,limit+(int)cyclelength);

for( i=limit+(int)cyclelength; i>=0; i--) {

........

Hurst[rates_total-1-i]=(cycle+b+10)*((sup-inf)/15)+inf;

........

My question is:

Is there any way to get the same behaviour in MT5 and MT4 version of the indicator?

Files:

battleplan.mq5 6 kb

battleplan_ciclo_4_tempi.mq4 4 kb

#2

If you remove the flag condition, then it works

1916×930 20.9 KB

What you have to check are the values (which are obviously not correct)

Files:

test_mq5.png 89 kb

#3

Sorry for confusion, but what I need is to translate in MT5 is this one:

Battleplan ciclo 3 tempi.mq4

As you can see in the picture the indicator in mt4 draw the battlepla also for future data (the battleplan is shifted in the future of “cyclelength” period ). How can I get the same in Mt5?

Regards,

1020×414 74.7 KB

Files:

battleplan_ciclo_3_tempi.mq4 3 kb

battleplan.jpg 88 kb

#4

I solved the problem with a workeround

battleplan_ciclo_normale.mq5

743×445 59.8 KB

Files:

battleplan_ciclo_normale.mq5 9 kb

a.jpg 72 kb

#5

Hi Cristi Ruddiforth, I tried installing the battlepan indicator on my mt4 but it does not work. I see nothing, maybe something wrong. can you give me any advice? thank you

#6

Check for errors in the logs.

Also you may want to add #property strict directive in front of the source code, recompile it, and try again - this can help to pinpoint possible problems.