Elite indicators :) - page 733

Mladen Rakic
151615
Mladen Rakic  
blueeagle
948
blueeagle  
mladen:
tamaraofx Tested it now and it all works OK (that is a public indicator that anybody can download). Please try again.

Hi mladen,

I still cannot access that thread. Please update my access rights to the public folders.

Thanks,

Mladen Rakic
151615
Mladen Rakic  
tamaraofx:
Hi mladen,

I still cannot access that thread. Please update my access rights to the public folders.

Thanks,

Checked it and rechecked it and all seems OK (nothing needs to be altered as far as your access rights are concerned). Try cleanig your browser cache as a first step. Also check your PM box

Mladen Rakic
151615
Mladen Rakic  
nevar:
I think this is what is hapenning : https://www.mql5.com/en/forum/181280/page17

Here is for example a range oscillator with bands made to be strict compatible too. It will not work on older versions of metatrader 4, and if they decide to change something again, it might stop working with some new build too (metaquotes have proved numerous times that they could not care less for downwards compatibility)

Try to debug this one now : range_osc_with__bands_arrows_nmc_2.mq4

_________________________

PS: I tested it with debugger and it worked OK. But do not be surprised if your debugger freezes if you have break points (that is more or less a rule of thumb - if you set a break point anywhere in the source and you try to switch to the main chart while debuging, metatrader will freeze - you have to remove break points in order to let it work again) or if in some future version all of a sudden this version starts to behave weird

Been on that road with metatrader 5 and sometimes it was harder to find what the hell did they change that started to cause errors that time than to find hairs on Heidi Klum's chest

Mladen Rakic
151615
Mladen Rakic  

Noticed an error in the last version of absolute strength of averages

The error was happening when sma was used for averaging (only in that case). This is a corrected version in which now all the 20 possible averaging methods are working correctly : absolutestrength_of_averages_mtf_2.06_nmc.mq4

William Snyder
9496
William Snyder  

Force Histo Smoothed_mtf+alerts+divergence from here: https://www.mql5.com/en/forum/general updated to be compatible with new mt4 builds.

nevar
468
nevar  
mladen:
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)

Mladen

How can I choose the other mode other than the strict mode?hanks.

William Snyder
9496
William Snyder  

Coppock curve - averages & alerts from here: https://www.mql5.com/en/forum/general updated to be compatible with new mt4 builds.

Mladen Rakic
151615
Mladen Rakic  
nevar:
Mladen How can I choose the other mode other than the strict mode?hanks.

In debugger you can not. It simply is not meant to work in anything but a strict mode.

In code it is done by specifying #property strict but then also a lot of much more serious code rewriting follows (and often you depend on your intuition only in that process)

Mladen Rakic
151615
Mladen Rakic  

This is an advanced version of the NinjaTrader like T3 indicator (it was posted here : https://www.mql5.com/en/forum/173058/page27 ).

The addition is that it can calculate Fulks/Matulich way of calculating T3 too (when T3Original is set to false) or Tim Tillson's (the inventor of T3) way if it i is set to true. Fuks/Matulich way is "faster" (less lag). Maximum count for calculation is limited to 25 (for practical reasons)

t3_nt_advanced.mq4

The example is showing 6 T3 instances with same parameters except that count is set from 1 to 6