The doc for dsGetTickValue() says:
"This function uses an algorithm that is very accurate when used in conjunction with intraday bars but less accurate when used with daily bars or larger. In addition, the algorithm is rather processor intensive so this function should be called only when really needed. "
Huh???
The specs.tab file has all of the minimum tick values for futures contracts. eSignal charting already relies on this file for the ruler and the y-axis labeling.
How about replacing Chris's 'algorithm' with the same easy lookup that you do anyway as part of creating a chart? There shouldn't be any guesswork involved and the simple answer retrieved by this function should not have anything to do with what timeframe it's retrieved on or be "processor intensive".
In fact, it should probably be extended to allow me to find the minimum tick value of any symbol, no matter if it's the currently charted symbol or not.
"This function uses an algorithm that is very accurate when used in conjunction with intraday bars but less accurate when used with daily bars or larger. In addition, the algorithm is rather processor intensive so this function should be called only when really needed. "
Huh???
The specs.tab file has all of the minimum tick values for futures contracts. eSignal charting already relies on this file for the ruler and the y-axis labeling.
How about replacing Chris's 'algorithm' with the same easy lookup that you do anyway as part of creating a chart? There shouldn't be any guesswork involved and the simple answer retrieved by this function should not have anything to do with what timeframe it's retrieved on or be "processor intensive".
In fact, it should probably be extended to allow me to find the minimum tick value of any symbol, no matter if it's the currently charted symbol or not.
Comment