If the history is
deleted then both methods produce the same number of bars in the history and
the right click Refresh does not increase the history length. However, if there
is an existing history both methods still give the same amount of bars but the Refresh
method then works harder to fill in gaps in the history, making the bars length
longer.
I conclude that
either method works for recent data, although the ArrayCopyRates method seems
simpler and computationally less expensive. Neither method gives the fullest possible
history data but if used sufficiently often there should be no missing data. (This
becomes problematic on the lowest timeframes).
The iShow indicator is a dummy indicator. Well mostly it draws a histogram of values I pass to it via globalvariableset(), so it's useless for analysis before the point of attached. I was not sure if this method would have worked. I know it worked in the back-tester for getting data for other Symbols/Timeframes when I wanted to test an EA which was influenced by events happening in other Pairs.
Anyways good job on all the tests and results. Tho I don't play around much with creating Indicators and PostMessageA features, it's never too late to learn and I appreciate your examples.
Ok, so I have tested Uzben’s iCustom method against the ArrayCopyRates method.
I have had to create a dummy indicator which does as little work as possible in order to test the Uzben’s method.
I have also tweaked Uzben’s code to use the new indicator and to suit my own aesthetic preferences.
If the history is deleted then both methods produce the same number of bars in the history and the right click Refresh does not increase the history length. However, if there is an existing history both methods still give the same amount of bars but the Refresh method then works harder to fill in gaps in the history, making the bars length longer.
I conclude that either method works for recent data, although the ArrayCopyRates method seems simpler and computationally less expensive. Neither method gives the fullest possible history data but if used sufficiently often there should be no missing data. (This becomes problematic on the lowest timeframes).
The iShow indicator is a dummy indicator. Well mostly it draws a histogram of values I pass to it via globalvariableset(), so it's useless for analysis before the point of attached. I was not sure if this method would have worked. I know it worked in the back-tester for getting data for other Symbols/Timeframes when I wanted to test an EA which was influenced by events happening in other Pairs.
Anyways good job on all the tests and results. Tho I don't play around much with creating Indicators and PostMessageA features, it's never too late to learn and I appreciate your examples.