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)
what is eswingrays? Searching futures.io (formerly BMT) did not reveal anything. Swingrays...are just NT"s own Swings which end only when they are broken.
EDGE:
I contacted NT support and will be back with an answer as soon as they tell me..
Can you help answer these questions from other members on NexusFi?
Heya Blue, ol' buddy... :beer: I've been try'n to catch up on some reading all day, but seems like other things keep pop'n up.. Anyway, hopefully now I can get back to it and thought I'd take a moment to share... I did some personal …
I just took the swingrays2 indy that was posted here on the forums and hacked it up to try and fix some things I didn't like about how it was working, then also added the ray labeling to it. I just named it eswingrays because that's how I name all my personal modifications to not confuse things, but I had nothing to do with the original code. I did look at the code that Eubie is using, and to be honest, it does look much more efficient! He should prob take the labeling portion out of the one I modified, or add something similar (as I'm not sure just how efficiently I did that) and then once he gets those values exposed, his modified version would probably be a better alternative to the one I posted..
Thanks for try'n, but still no luck.. Not sure why, looks like it should work to me.. but I get this when printing values from another indy..
Using a dataseries is probably the better method if you ever want to see anything other than just the very last value.
But if anyone is going to try and get this to work, please properly expose the swing hi/lo's and bar#'s values as well.
Also any updates should probably be renamed to swingrays3beta or something (anything) new so that no one confuses this with what is already posted on the forums, or doesn't overwrite an existing indy.. Thanks!
where the accessed variable is said not to be allocated yet. However, as it's an int, there is no need to dynamically allocate it, so both me, Bertrand and now probably even you are surprised
I tried making a version with dataseries, but the problem was the same. Thank you for the interest though
Wow this is an old thread I'd forgot all about.. Came across a post in Want your NT indicator created for free that was asking if someone would expose the values in this indy and even referred back to this thread.. Since I just posted a revised version over there, thought I might as well post it here in the original thread it started in.. I cleaned up the code a bit and exposed the last swing high and low values so that it could be used in a strategy or bloodhound.. None the less this was some pretty old code, and could still use some more cleaning up.. Didn't spend a lot of time on it, as it's several years old and about 10 versions behind what I'm currently using .. But here ya go.. Enjoy!
