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)
Thank you for your reply.
I apologize if I am coming back even after your "last thing" paragraph, but as per your kind suggestion I have asked a consultancy to a programmer, (I understand with very extensive NT programming experience), for modifying your popular divergence indicator, so that one can get trading signals executable into a the strategy wizard. Unfortunately the response I got has been that it was not worthwhile the effort since this indicator appears to repaint (I do not know exactly what this means, anyway I undertand this is supposed to be a problem) and any time one changes the chart timeframe it resets its oscillator input series back to the price input series. I would be really grateful if you could let me (and any other newbie possibly interested in this) know whether you think you may fix these issues, .... when you have a some spare time to dedicate at it. Alternatively if you know a programmer who could do these upgrades to your indicator wouold you please ask him/her to pm me for a quote.
Thank you. Best Regards.
guidoisot
If you compute divergences while the bar is evolving, you need to accept that a divergence may occur ..and disappear.. before the bar is closed. Since we don't know how the bar will be closed when a signal occurs, we repaint over and over the divergence when we have a signal, or do not draw (erase it..) when it does not appear... This is called repainting.
However, if you set the compute on close to true, then the computation is done only once, on the close of the bar. And there is no repainting...
Again, ECIDiv was built for discretionary traders. And, at least "some of them" want the signal to be known as soon as possible because they see it as an advantage, not a issue or a problem ...
If you are not interested in repainting, simply set the compute on close to true.
Regarding time frame change... I have no problem with that. I do have the problem we talked about of Ninja not reloading properly the parameters when you reload a workspace you just closed without a reboot. Still need to contact Ninja about this in order to understand why the don't restore properly the parameters (it may be in my code, but ninja code does the save/restore .. not the study code).