Suggestions / Comments

[byzantium]

Suggestions / Comments:
1. Put a "Are You Sure" message box behind the "Delete" button for instrument lists. I deleted an instrument list by accident.
2. Exit on close, and high-level function SetTrailStop() are great.
3. It's a hassel to download the same instrument data when backtesting each time you re-open the strategy analyzer (try downloading several years of 1 minute data for nz 100 from open tick).
4. Make more of the strategy analyzer settings persist from session to session (or make them settable from code). Ex: Session Begin / End time.
5. The biggie...get a real debug environment. I certainly would pay for it. There are a lot of great features in the system, but to do complicated strategy development it's really necessary to step through code. I really like SmartQuant's approach, but they don't have your ease of use. They don't have a debug environment either, but at least you can attach Visual Studio, and step through the code.

All in all, very nice product.

Hello,

Thank you for your suggestions and comments. I will forward them to development and ahve them add it to our future enhancement list.

[VagyokC4]

I AGREE! There are times when the ability to step through the code line-by-line when building advanced strategies would be so helpful.

Can we put a POLL on this questions to see if we can get it bumped up the list.

[NinjaTrader_Dierk]

Unfortunately this is a .NET limitation where NT can't do anything about it.

[VagyokC4]

But in dotNET you can attach a debugger and step through the code... I do this all the time?... and SmartQuant is doing it

[NinjaTrader_Dierk]

We debug here all the time too. That's not the issue. The issue is that you can not debug a DEBUG build of your custom DLL (which is loaded dynamically) from a RELEASE build of NT without loosing all the valuable DEBUG info from your custom DLL.