winsig.exe and kernell32.dll errors

[mbuta]

Hi,

(If this is a duplicate posting, sorry, but cant find the first one).

Quite often, when changing time intervals, or symbols, or in pre/post market, eSignal crashes with the errors above.
The only way to recover is to either delete the charts, layout, or sometimes, to delete the eSignal and re-install it.

At the time, other layouts work with the same indicators.
It seems that a null value, somewhere, corrupts some files (as explained by eSignal representatives).

Null are part of life with the Internet and streaming data and some get(xxx) with catch a null somwhere, sometime.

Is there a way to avoid the crashes and file corruption when that happens? (checking for null in 300-400 places does not seem like the best idea)
Are there any plans to make efs environment more resilient to nulls and other errors? Is there a way to (gracefully) recover from such errors?

Thank you,
Mihai Buta

[JayF]

Mihai,

Null checks are a necessary part of creating robust code that will function under a variety of conditions. This is standard coding practice as are checks for dividing by zero, square root of a negative number, etc.

However at the same time, when such an event occurs our code should be written to also be forgiving. I will pass along this thread as a request to make changes in this area of the EFS engine.