Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
In Simulation you can change colors on the chart trader and the Dom, but for live trading everything is stark.... white except the option to color a few buttons. I get bad eye strain with all that white . I would like to have the option to have at least one dark shade of grey for live trading and if you can make that color option match the outside borders of all the charts I have open also.
To be able to easily distinguish when trading live or sim I would like to see the word LIVE appear on my Dom and my chart trader somewhere it could even flash or something to make it really easy to see.
Thanks Quantismo
Can you help answer these questions from other members on NexusFi?
1. User interface (UI) parameter fields are selectable via a tab or arrow key.
2. Display mode (currency percent ...etc) stays were it was last set.
3. Strategy Analyzer (SA) Start and Stop dates can be batched in a file. Each press of the run button sequences the next date pair.
4. Strategies start with indicators fully wound up on the start date.
5. Chart in fixed scale mode remains vertically visible while scrolling.
6. SA abort should be instantaneous.
7. SA summary should include a buy and hold parameter.
8. SA graphs should include a chart overlay of the users choice.
9. Strategies should be able to detect "Account Unavailable" condition.
10. NT should be able to restart itself and reestablish running strategies to work around broker server resets.
11. Option to suppress all pop up messages and warnings. Put them in a mailbox and not take focus.
12. NT strategies should be capable of running 24/7 without 3rd party software.
13. Option for Stoploss and Profit Target simulated to allow bracket trades for certain brokers.
14. A trade time aperture so NT can handle trades from brokers that submit positions before executions (ie. MB Trading).
15. SA Start and Stop fields should be in a fixed location so an automated keystroke generator can service them.
I believe this exists already and has for a long time. Just right-click in the grid and hit export to excel. If what is included isn't enough, then you can write your own NinjaScript to export whatever you want.
A more robust fault resistant platform where if 1 chart red x's, drops, or dies you dont have to reload the whole thing
When you clear your MARKET DATA out IT DOESNT DELETE YOUR STRATEGIES YOU'VE SET UP IN CHARTS
Why on earth do we have to kluge Gomi's recorder or Richard Todds extended data dll to get to the extended data?
Make chart types just like indicators so we can name them what ever we want rather than the limited predefined options.
Hire, ask, do what you have to have 3 months of Richard Todd's time for programming.
Provide cheep and easy server hosting, doesnt have to be colocated but if it's close and the right price point, you would pick up a new revenue stream.
Is there a weekly or daily max stoploss in the ATM? If not, add it.
The present implementation of the Fibonacci indicator is very cumbersome. In order to delete partial lines, you have to go into the whole setup and "untick" the ones that are irrelevant or passed. I suggest the following:
1. After placing a Fibonacci calculation on the chart, allow DELETION of any one of the lines by placing the mouse on the line and pressing DELETE. This is similar to the deletion of any other line on the charts.
The above is such a small change but a large benefit and user friendly change.
When you abort an optimization, it would be great if it would just abandon the iteration that it's working on at the moment, and display all of the optimizations that were completed up to that point
This is mainly referring to the times when you start an optimization run, and realize right after clicking that you forgot to change some parameter.... It's incredibly frustrating to start an optimization on a complex strategy, and then have to sit through 5 mins until the first iteration completes. I would rather lose whatever NinjaTrader has calculated to that point, than waste time waiting for it to finish a run that I've already said that I want it to abort.
Platform: "I trade, therefore, I AM!"; Theme Song: "Atomic Dog!"
Trading: EMD, 6J, ZB
Posts: 795 since Oct 2009
1) some means of knowing, either as line entry on log, trace or error file, of missing components, indicators or reference assemblies when loading a template.
at present, there is no notice of what might be missing, when using a template or sharing one, and one doesn't know... close the gap and notify, so the missing component can be known, searched for or obtained
2) provide an auto-save function at some user defined interval, such as every 5mins or so, so that any work done, and an abort, power outage or otherwise disrupts normal function of the platform, then the checkpoint or save of state can reload from that point instead of all work being lost
3) even if simplistically, offer some form of "best practices", or "suggestions" as to why the platform takes 8 minutes to load, and what's holding it up, when a normal start up takes less than 2 minutes
just some thoughts, probably previously mentioned, but much needed to significantly improve the stability of and usage of the platform
keep innovating, it has become cutting edge and well above the other platforms....
Platform: "I trade, therefore, I AM!"; Theme Song: "Atomic Dog!"
Trading: EMD, 6J, ZB
Posts: 795 since Oct 2009
some means of recovery when the platform hangs,
in software development, there usually are global variables to trap errors that happen deep within the sub-sub-subprograms,
perhaps there needs to be an initial global over the entire application so that trap and trace (error reporting method) can be employed, so that upon recovery there is/are some means of finding out what happened that lead to the platform becoming frozen and not recovering or responding
whether its an out of control function, zero divide error, non responsive function, bad data from the servers or broker data feed or whatever
that combined with a system configured auto save function would at least attempt to preserve the state, charts, workspace and whatever other work done up to that last interim checkpoint would make the frequent inevitability of frozen platform, more endure-able
at present, one looses and doesn't recover, unless they took notes in advance and anticipated a failure of station or platform