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 was thinking along the same lines recently. I don't suppose Mike would have a problem, but I was considering posting / updating the indicators by editing my original (post #1) post, instead of creating new posts all the time. I can see where this is starting to get away from me & probably getting very confusing for the other members. The various versions, although similar, all use the same logic in determining whether to go long or short. It's just a matter of refinement & finding the best of the best. Rjay found that the DoubleMAPaint indicators were repainting, Mike chimed in with some suggestions & Rjay posted a fix today that addresses that problem when they are used as "bar" type indicators (in panel 2, 3, 4, etc) instead of 'line' type indicators, as they were designed to be used, in panel #1. I still want to do more replay testing of the DMAP indicators over the weekend, as they were originally my favorites. In the past few days I've also been testing Rjay's modified T3AverageOverUnder and SeansAverageOverUnder and SeansAverageUpDown. I want to see what gives the best signals.
After all, it's what you learn AFTER you know it all, that counts!
Can you help answer these questions from other members on NexusFi?
Telly, You're right! Rjay found the same & posted a fix for the code of the indicators that were 're-painting'. I made the code changes in the indicators on my computer & plan on doing some replay testing over the next day or so before posting and updated version. I think we'll all get there - eventually!
After all, it's what you learn AFTER you know it all, that counts!
One request though for all code makers and code adapters. If you change an indicator code pls. add some info at the beginning of the indicator_file what&where you modified the code. That way it is easier for others to follow what changed throughout the different versions. As example see e.g. in the DMAPaint code.
Also and even more important. If you change a code in an existing indicator make sureyou change the name. E.g. some 'line' indicators can be improved for use as 'bar' indicator by commenting out some code as mentioned earlier in this thread. Make sure that after that change the indicator is saved under a new name. (e.g. by adding '_bar' to the name).
If this is not done systematically we could get identically named indicators that behave differently, e.g. a Sean avg. or a DMAPaint that doesn't paint as the original anymore in 'line' mode.
Experience tell us that this would lead to confusion and loads of mails from less involved users that their screen looks different.
So everybody ... pls. change the name and add info if you adapt code!
Thanks for this great thread, am very keen to follow these indicators, my main concern is that of the repainting - has this been resolved ? Which template should be used to avoid this ? Any input would be greatly appreciate. Kind regards, Lee
