Elite indicators :) - page 712

 

The less lag version Digital filters - trend score from here: https://www.mql5.com/en/forum/general updated to be compatible with new mt4 builds.

 

newtrader100

Overlooked it, sorry. Here you go

It is set by default to alert when 3 digital filters slope points in the same direction. You can additionally set weights for every of the digital filters and alerting level (level 2 with weights all set to 1 means 3 in the same direction since the score is calculated in the following manner : up slope +1, down slope -1; so, for example a UUDU is +1+1-1+1=+2)
regards

Mladen

newtrader100:
mladen,

If you're too busy and/or don't believe my previous request would be worthwile, please disregard.

Thanks.

updated version here: https://www.mql5.com/en/forum/general

 

Range osc with bands_arrows from here: https://www.mql5.com/en/forum/general updated to be compatible with new mt4 builds.

 
biddick:
Hi Mladen , To make it more meaningful, is it possible for you to add bands and signals(std dev.band crossings) to range oscillator?Thanks and regards.

Changed out the Wpr with the Range osc!

ps)Just reread your post will try and add the signals!

Added the arrows code!

updated version here: https://www.mql5.com/en/forum/general

 

Hi Mrtools,

I get same error warning for both Range osc with bands_arrows and mtf Cci on jurik with bands_arrows_alerts indicators,

can you check?

Files:
ekran_alnts.png  35 kb
 

I get same error message with some elite indicators.I have MT4 625 built platform.

 
nevar:
I get same error message with some elite indicators.I have MT4 625 built platform.

Nevar, is this with an offline chart because I'm using build 625 and not getting that error.

ps) just looked again at your post, looks like your using regular hourly charts, not sure what is causing the error.

 

That error comes because debugger always uses code as if it is compiled using strict mode (it does not know the difference when the code is compiled as strict and without ot)

For a moment it is not wise to use strict mode (they are changing the rules with each and every new build and completely unpredictable things happen then)

 

Just a simple example : see what happens when metatquotes changes the rules on the fly : https://www.mql5.com/en/forum/181297/page48 and when all the previous work goes down the drain

Upper is how a good deal of Nikolaj Kositsins code at mql5 code base works now and lower is how it worked before they "improved" metatrader 5 (not metatrader 4). So the story about metatrader 4 is probably going to look like the metatader 5 story and since metatrader 5 always works in strict mode, if we use it, the conclusion is obvious

In my opinion, for now avoid the strict mode. Nasty surprises are still ahead of us

Files:
k1.gif  51 kb
k2.png  19 kb
 

I am nearly done with MT4/5 ,I am looking for Oanda/API solution.Look at the below charts.The Russians dont have respect for what they do:

Files:
Reason: