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)
Probably safe to say that this level of discussion does not really belong in this thread--there are tons of threads on both the ninjatrader support forum and on this site on how to import indicators and CS. Use what is available and learn how to search for your own answers when there are already tons of resources out there.
Can you help answer these questions from other members on NexusFi?
keep calm josh and make your indoctrination to your children. if it would be so easy for me to import with a little bit of googeling i would have done. if this question makes you head shaking, OVERREAD it and safe your time for writing this kind of answer for more important things.
Phillip the original binary did not include a source option. If you still have the original assembly it won't show it.
Take these steps:
1. Go to File->Utilities->Remove Ninjascript Assembly
2. Remove the previous OneLDOM assembly. Highlight it and click -> OK.
3. Now go to your folder files and copy the OneLDOM.CS file and paste it into the this directory:
4. When you go into Ninja now and edit indicator you will see OneLDom in there and you can click on it and open it and compile it. You will need to make the compilation step with this approach for it to work.
If you are not comfortable with this I have put a new assembly on my blog of V1.5 and that set of steps is easier. Just remove your old assembly then import the new one as is the normal case.
* EDIT * -> Let me know when you have achieved this, then maybe we delete these small set of posts so we can keep the thread quick and to the point for others.
How certain are you that you have the latest compilation and are not running an old binary?
That error message is no longer possible in the latest version as I actually completely removed the offending code.
Also what market?
VVHG you helped me find the problem originally and were able to confirm both the initial issue and the version working with the offending code switched off. Have you had a chance to run the latest code set to see if it is operating as you expected now?
I have downloaded and installed the version OLDomV1.5 from your website including the template. However when I loaded the chart with that template, there was no indicator there so I have to load the OneLDOM indicator manually.
Is this usual or could this be the reason for getting only the blue screen?
As someone that knows a fair amount about TT, it's patent and the way it pursues infringement cases, I would urge you to tread very carefully here.
1 - Should this project become the 'clone' of XTtrader the posts in this thread imply, you will more than likely be hearing from TT. You have already cloned the appearance to some extent.
2 - By doing this work as individuals, you become personally liable for the infringement. Behind a corporation, you put the corporations assets at risk, with no corporation, it's your personal assets.
3 - By doing this as shareware, the usual resolution for infringement (payment of royalties to TT) is not available to you. You have no control of the licenses, you have no idea who's using it, therefore you can't move your users to a version that collects royalties.
4 - The posts in this thread so far will make TTs job very easy were it to ever get to court. The more people request and add in TTs features, the stronger their case becomes.
I personally disagree strongly with the TT patent but it is what it is.
I'd think long and hard before you put your personal assets on the line for a shareware clone of their product.