Separate threads for indicators / UI

[Currywurst]

A suggestion for maybe NT 7 (which is supposed to provide full multi-core support):

Try to separate indicator calculations and UI thread. The indicators should not be calculated in the UI thread.

I noticed the crosshair lags when using many or complex indicators (a bunch of WMAs for example). So I assume the indicators are being calculated in the UI thread, or at least, the drawing and calculations are being processed in the same thread.

So two separate threads would be nice. The UI should always respond instantly, no matter how many complex indicators are being calculated.

[NinjaTrader_Dierk]

Thanks for your suggestion. We'll add it to the list of future considerations.

[Currywurst]

Just an addition due to http://www.ninjatrader-support.com/v...486#post30486:

Not only indicators should be calculated in another thread. The rendering itself should be performed in another thread, too. Maybe indicator by indicator. Only the actual drawing (not rendering!) to the UI should happen in the UI thread.

This way the UI should always respond, no matter how complex the calculations/rendering might be.

[NinjaTrader_Dierk]

>> The rendering itself should be performed in another thread, too
Please consult the MS documentation to learn that ANY UI processing/drawing needs to run in the app's main thread.

[Currywurst]

>> The rendering itself should be performed in another thread, too
Please consult the MS documentation to learn that ANY UI processing/drawing needs to run in the app's main thread.

That's why I wrote:
Only the actual drawing (not rendering!) to the UI should happen in the UI thread.

Any time-consuming processing should not be performed in the UI thread to avoid blocking.

The actual chart could be rendered asynchronously and should be cached. The UI should only repaint the cached chart.

[NinjaTrader_Dierk]

Thanks for your suggestion. We'll add it to the list of future considerations.