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)
A naming convention for indicators that causes them to be logically grouped in the list of indicators that appears when indicators are added to a chart. Use a military style naming convention with names containing group categorization followed by spaces and punctuation characters in the this. Name property. For example, all Moving Averages would be grouped together because the this.Name property for every one would begin with the string "MA, ". All Oscillator names would begin with "Oscillator, " etc (See attachment)
The option of reporting trades either as reported by the exchange, or of re-bundling as one trade those transactions that happen within 1/100 of a second of each other.
The ability in the FormatPriceMarker method to apply multiple custom formats and values when an indicator has multiple plots, instead of being forced to format and value all the markers identically.
The ability to EXACTLY CLONE a chart, including all DataSeries settings.
Combining the Bid, Ask, and Last files into one file that is properly sequenced and has millisecond time stamps based on EXCHANGE time.
Providing for batch updating of replay data for a date range and for a number of instruments, instead of current method of one instrument at a time, one day at a time.
Providing for the handling of stack overflow errors without crashing the application.... can this be done?
Can you help answer these questions from other members on NexusFi?
I didn't check thoroughly, but it appears that Bars.Count includes all downloaded bars (including extended session), so if I'm not displaying it, CurrentBar + 1 will always be smaller. We'd need a built-in read-only boolean property of Strategy denoting last bar on chart (properly considering session template settings as well as the end date I set in Data Series properties dialog which may be in the past).
You need to have a idiot box popup box when closing out a chart. I cant tell you how many times I have accidently closed out a chart and lost my work.
Something like:
If I click yes:
If I click yes again:
Then close out the chart.
Well, I went a little overboard, but you get the point. With something as important as a chart where live trades are happening there really should be at least one safeguard. One last chance to say no, I didnt mean it...
Yes, I quickly close Ninja Trader, don't save workspace and then open it back up. It is a big pain in the arse.. and Shift F4 is close the active chart???? Why can I not change that??????
Please make it tailorable to the trader. I am much more deliberate with my actions and don't need the extra impediments to me doing what I wanted to do.
It would be nice if Ninja could use multi core CPU a lot more. I use I7 CPU and it use max 15% and are very heavy to start becouse of some simpel data calculation in MarketAnalyzer and on chart. Why not let this go to different core.?