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)
Striving to get as much stuff working on Ninja Trader 7 as possiblle will give this forum's members more impact on what Ninja Trader Produces as the offical release of NT 7.01
Currently, collecting a list of Indicators that are incompatable when moved from 6.5 top 7. Some of it code break stuff and easy. If I see enough of them I'll develop a feel for the easy vs. hard fixes.
Really important suff like the 1000 time down-loaded Murray Math I took to NT support and had a fix in minutes. For other, like adapting Big Mike's futures.io (formerly BMT)EnvelopExpander to 7, I asked one of the really good coders on the Forum and he gave me an answer that allow me to have a compiled version in less than a minute.
I will do my best. Proirities are Highest # of downloads, what the other Modererators feel is important and what ever Big Mike wants done. Not necessarly in that order.
If we keep the majority of Beta stuff in this thread & other development threads and working suff in the download section (please put all indicators, workspaces, etc. in the download section, and remember your key words, please) and just link it to the thread it will be easier for everyone to find stuff.
The point of this post is to show that even I can do this. So you can to.
The biggest changes between NT 6.5 & 7 is that the drawing elements and arrray are different. I'll leave the array stuff to real coders like Gomi, Zondor, RJay, Mike, Sharky, and the rest of you who are code artists.
But minor Code Breaks are easy to fix.
Take VolumeStopRefreshv4 that I changed to work with NT7
First import the indicator, then try to compile. You will get lots of error mostly to do with Draw statements.
One you get the error screen like shown below. Hit F1, then go to the search tab in the and type in the name of the element that has changed. In this case DrawText.
//DrawText(string tag, . . . . . . bool autoScale, string text, int barsAgo, double y, int yPixelOffset, Color textColor, Font font, StringAlignment alignment, Color outlineColor, Color areaColor, int areaOpacity)
I paste what I find below the line, comment it out and match up each field until I have spotted the problem. In this case true needs to be added, because there is now a auto scale field that is a bool type.
Do this for all the errors like DrawRay, DrawTriangle, etc. and eventually the code will compile.
Anyone see this type of error? When someone submits a non-working Indicator I will post the problem if it is something I have not seen before, in advance of my delving into the code blindly.