Scripts: ThirdPartyTicks - page 7

New comment
 
traveller00:

2. In the string ToCustomSymbol function, you don't see checks that the symbol already exists. To be honest, I didn't check what will happen, I didn't go into details. But for myself I've docked the check so that when I continue, it doesn't parse all the files for old existing symbols again.

It is specially made that way. The archive is updated with new data every day, so even if a symbol exists, it needs to be refilled.

Unfortunately, I can't manage to do the filling not from scratch yet. I haven't decided how to do it correctly yet, because the script has filters etc. built in.


But this circumstance does not cause any special problems, so this task is somewhere in the back of the priority list.

 
fxsaber:

specifically implemented a workaround. Since then, no brakes.

I haven't noticed why it can't parse the directory on each symbol again. Maybe they haven't posted an update. But if no one else complains, it works for you, and I've made it work, then fine.

fxsaber:

It's done that way on purpose. The archive is updated with new data every day, so even if a symbol exists, it needs to be refilled.

I suspected that was the case. I see your point, ok.

 
traveller00:

Didn't see why it might not parse the directory on each character anew.

In the script, the mass launch is done through the task

sinput string symbol = "AllSymbols"; // Symbol (NULL - current, "AllSymbols" - All)


Perhaps you have done it differently, so it was checking on each symbol.

 
Yes, everything is correct, AllSymbols is filled. The CreateAllSymbols(false, iMinPips) function is pulled; Inside it, the ThirdPartyTicks[i].ToCustomSymbol(Sync, where Sync is set true from the script parameters. And in the Update function, this.FilesOffline.Refresh() will be called for each symbol; which will parse the whole folder.
 

For some reason I got an array overrun.


What could this be related to?

 
Vasiliy Pushkaryov:

For some reason I got an array overrun.

What could this be related to?

There wasn't enough memory. There should be a system record about it in the Terminal Log tab.

To immediately understand when something like this happens, write this line at the beginning of the script.

#include <fxsaber\HistoryTicks\ArrayResize.mqh> // https://www.mql5.com/en/code/20298
 
fxsaber:

There was not enough memory. There should be a system entry about it in the Terminal Log tab.

To immediately understand when something like this happens, write this line at the beginning of the script.

Right. I freed up some space on the disc and it worked. Thank you.
 

It's writing a bunch of errors.

The darkness of error

 
BillionerClub:

It's writing a bunch of errors.


Check your site for sabotage and viruses, someone is constantly chewing data.

 
BillionerClub:

It's writing a bunch of errors.

Unfortunately, I can't update the code, the KB swears.

123456789101112131415
New comment