getCurrentBarIndex and setComputeOnClose

[clearpicks]

It seems in the new eSignal 10.0, if setComputeOnClose(true), the returned value of getCurrentBarIndex() of the last bar is 0, while in the older version eSignal, the main() is not executed on the last daily bar unless after the regular trading hour, therefore it always returned -1 during the trading hour. Am I correct?

It seems there are a few nuance changes in EFS in eSignal 10.0. Where can I find the documentation for all these changes?

Also when will the drawText flashing bug be fixed?

Thanks.

[ACM]

clearpicks
As far as I know there are no differences between 8.0 and 10.0 with regards to how setComnputeOnClose() works.
In both versions a script that includes the setComputeOnClose() statement will process one time only the most recent bar on a daily (or higher) interval and the last completed bar on intraday intervals. The enclosed screenshots captured using version 8.0 (top two scrennshots) and 10.0 (bottom two screenshots) should illustrate this
Alex

Originally posted by clearpicks
It seems in the new eSignal 10.0, if setComputeOnClose(true), the returned value of getCurrentBarIndex() of the last bar is 0, while in the older version eSignal, the main() is not executed on the last daily bar unless after the regular trading hour, therefore it always returned -1 during the trading hour. Am I correct?

It seems there are a few nuance changes in EFS in eSignal 10.0. Where can I find the documentation for all these changes?

Also when will the drawText flashing bug be fixed?

Thanks.

[eSignal_JasonK]

Re: getCurrentBarIndex and setComputeOnClose

Hello Clearpicks,

Originally posted by clearpicks

It seems there are a few nuance changes in EFS in eSignal 10.0. Where can I find the documentation for all these changes?

Everything done for 10.0 should be in the Readme.txt file.

Also when will the drawText flashing bug be fixed?

Thanks.

This is slated to be fixed in the next release.