[WARNING CLOSED!] Any newbie question, so as not to clutter up the forum. Professionals, don't go by. Can't go anywhere without you. - page 655
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Naturally, and when else.
mm, I thought, chunks of completed, well, there are 128 kilobytes merged - recorded. As it would be more correct in case of crash. Although for the story, of course, whatever.
I just couldn't figure it out, I was downloading, but there was nowhere to go until I closed the terminal ))
You can change this parameter in the inite, but in the start it is doubtful.
Thank you, because when the TF on the window changes, the indicator restarts, it means it is possible to re-color the buffers
And the point is - on any TF, the colour of lines corresponding to stochastics of other TFs is always the same colour. I.e. if the hourly stochastic is blue, let it be blue on all TFs.
Of course, we can assign buffers of the appropriate colour to the appropriate TF, but then the processing program becomes more complicated. And we want it to read one and the same buffer under all conditions.
Print() you need to put here first:
that, make sure that array c1b_1[i] is empty, so comparing in if zeros, understandably deals are not opened.And zeros there because the averaging period in function iMAOnArray(c1b,0,AvgB,0,MODE_SMA,i) (extern int AvgB=25;) is larger than the array c1b itself , ArrayResize(c1b,PeriodB ) (extern int PeriodB=20;), so it cannot average anything.
Yes, indeed "0", but what to do, tell me - it does not work both ways (and equal periods set) tried both options (new and old) Print("NormalizeDouble(c1b_1 ..., null returns (shows only c1b[i] value, all others including c1s[i] - zeros), help bring one of the options to a working state or at least share a hint, who will see the flaw?
New:
Old:
Entire:
Gentlemen, I am wondering, if I cycle through four timeframes to find a signal, will the data be called each time, with more CPU load than if there were, for example, four windows of the same indicator with different timeframes?
Gentlemen, I am wondering, if I loop through four timeframes to find the signal, will the data be called each time, with more CPU load than if there were, for example, four windows of the same indicator with different timeframes?
It depends on how it is implemented.
int TimeMassive[15, 30, 60, 240] ;
for(int k=0; k<4; K++)
{
timeframe= TimeMassive[k] ;
for(int i=0; i<limit; i++)
Buffer[i]= iMA(NULL, timeframe,..........................) ;
}
approximately like this without allocating memory for each timeframe
int TimeMassive[15, 30, 60, 240] ;
for(int k=0; k<4; K++)
{
timeframe= TimeMassive[k] ;
for(int i=0; i<limit; i++)
Buffer[i]= iMA(NULL, timeframe,..........................) ;
}
approximately like this without allocating memory for each timeframe
That's a bit more accurate