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)
I received the following comment on NT Kase Bars via PM:
The following is how the implementation works: when a tick arrives it is always included in the current bar. Once the bar is updated, the true range is checked, and if the target range is met or exceeded a new bar will be formed on the next tick. If that next tick is at the same price, then the open of the new bar would be equal to close of the previous bar. The next tick could be the same or a different price.
So, the question is once a target range is achieved for a bar, do you wait to start a new bar until the range of that bar is exceeded?
In looking closer at the output of TS, the next bar is always opened outside of the current bar. If that is what is desired, then technically the bar is not closed when the target range is met, but only when it would be exceeded, and the new tick that exceeded the target range is part of the next bar.
I can easily change this, but Dan, perhaps you could comment first on how it should work. Thanks.
After playing around with TS, I went ahead and changed the NT Kase Bar implementation to only close the bar when the range is exceeded, and now it should match up with the TS version. There is a new version (V2) in the download section.
And thats why I hate Ninja, even something simple is not simple.
The problem is you have another bar type that is conflicting. In NT65, they use a routine called SortOrder() to return an integer that they use to arrange the sort order of all of the bar types. That is all and good, but nobody knows what other people use. Now, I used the next available even number, which in hindsight, was bad on my part because that is what everyone else does.
Try the following: Edit the KaseBarsType.cs file in the Type dir, and change the "14000" to "14123", and save the file, then edit any indicator, and compile it, then restart NT. That should fix your problem. If it does, I will update the file in the download section so others dont run into the issue.
I tried editing the .cs file as suggested above, but the exact same error continues to come up - I am assuming that I did everything correct.
Until or if the Kase bar type file is "fixed" can someone tell me how to delete all related files so the error will not come up any more? I have attempted to delete all the files that I could find, but the error continues to pop up.
Thanks for a valiante effort and I look forward to the updated file.