- Time is often non-null, but still invalid, so that does not work
- Time.Count throws if accessed before Time is valid. Technically one could do a try...catch, but that is not really a very satisfactory method
- I know from the debugger that Time is sometimes valid and sometimes NULL when State >=State.Historical. I do not like a state-based method anyway, because it is subject to breaking in the future if the implementation changes
- ISeries supports IsValidDataPoint(0), but unfortunately TimeSeries does not
What I am really looking for is a way to directly test whether or not Time is yet valid. Any suggestions will be appreciated.
Thanks,
--EV
Comment