One more average ... - page 29

talaate
967
talaate  
mrtools:
Hi Talaat E, added mtf with interpolation option and with the arrowOnFirstBar option too.

fatl_one_more_average_slope_speed_alerts_mtf.mq4

Dear my friend Mrtools, I would like say many thanks,

My regards

Jozy K
212
Jozy K  
mrtools:

Jozy, added options for zero cross and or slope alerts.

fatl_one_more_average_slope_speed_alerts.mq4

I am most grateful, Mrtools.

Mladen Rakic
163124
Mladen Rakic  

I hare when we do not have an option to chose price, se here is this one with the usual set of 20 prices as a possible choices added )it does not use a fixed close price any more) : fatl_one_more_average_slope_speed_alerts_mtf_2.mq4

techmac
2973
techmac  
plodds:
Re: Indicator Modification

i was wondering if sir mladen or any kind hearted person here could code divergence and divergence alerts into this timing indicator...

secondly, i have problems loading trendstrenght oma indicator into my chart as it has simply refused to show up each time i load it. thanks guys

Isn't "MBFX timing simply an rsx?

Mladen Rakic
163124
Mladen Rakic  
techmac:
Isn't "MBFX timing simply an rsx?

Yes it is :

Files:
mbfx.png 124 kb
techmac
2973
techmac  
mladen:

Yes it is :

Yep. Same old story ...

pavaka
4412
pavaka  
mladen:

Yes it is :

colors are slightly different...light green - dark green etc...

albry
68
albry  
mladen:
I hare when we do not have an option to chose price, se here is this one with the usual set of 20 prices as a possible choices added )it does not use a fixed close price any more) : fatl_one_more_average_slope_speed_alerts_mtf_2.mq4

Hi,

I have had problems with several indicators that have a similar general structure as this indicator, and there are 2 sections that cause them to crash in my environment, but for some reason they work in yours?

These 2 problems are in the following sections of code:

1) In the main routine for the current timeframe (i.e. TimeFrame parameter = 0) :

int limit=MathMin(Bars-counted_bars,Bars-1);

if (returnBars) { diffhuu[0] = limit; return(0); }

if (TimeFrame==Period())

{

for (int i=limit; i>=0; i--)

{

prices = getPrice(Price,Open,Close,High,Low,i);

double fatl = +0.4360409450*prices +0.3658689069*prices +0.2460452079*prices ... <=== right here, i+2, when limit=Bars-1 will be outside the price[] array bounds and crashes.

To fix these I would have to go through the indicators and figure out the max range outside of the array the routine goes and adjust the limit (or similar), e.g. limit=MathMin(Bars-counted_bars, Bars-38-1) for this indicator, or often correct by the moving average or sum of moving averages in other indicators. And then so that it displays properly at start of timeseries, also then need to add some additional code (e.g. SetIndexDrawBegin or similar). This same issue would also have to be adjusted in the multi-timeframe handling if "limit" or similar array bound was used.

2) and in the multi-timeframe handling (i.e. TimeFrame parameter = HTF than the current one)

for (i=limit;i>=0; i--)

{

......

if (!Interpolate || y==iBarShift(NULL,TimeFrame,Time)) continue; <=== right here, i-1 when i=0 will be outside the Time[] array and crashes.

Not sure why they don't crash on you too?

Is there something I should be doing to get these indicators to work properly?

Thanks for your help !

Mladen Rakic
163124
Mladen Rakic  
profitabl:

Hi,

I have had problems with several indicators that have a similar general structure as this indicator, and there are 2 sections that cause them to crash in my environment, but for some reason they work in yours?

These 2 problems are in the following sections of code:

1) In the main routine for the current timeframe (i.e. TimeFrame parameter = 0) :

int limit=MathMin(Bars-counted_bars,Bars-1);

if (returnBars) { diffhuu[0] = limit; return(0); }

if (TimeFrame==Period())

{

for (int i=limit; i>=0; i--)

{

prices = getPrice(Price,Open,Close,High,Low,i);

double fatl = +0.4360409450*prices +0.3658689069*prices +0.2460452079*prices ... <=== right here, i+2, when limit=Bars-1 will be outside the price[] array bounds and crashes.

To fix these I would have to go through the indicators and figure out the max range outside of the array the routine goes and adjust the limit (or similar), e.g. limit=MathMin(Bars-counted_bars, Bars-38-1) for this indicator, or often correct by the moving average or sum of moving averages in other indicators. And then so that it displays properly at start of timeseries, also then need to add some additional code (e.g. SetIndexDrawBegin or similar). This same issue would also have to be adjusted in the multi-timeframe handling if "limit" or similar array bound was used.

2) and in the multi-timeframe handling (i.e. TimeFrame parameter = HTF than the current one)

for (i=limit;i>=0; i--)

{

......

if (!Interpolate || y==iBarShift(NULL,TimeFrame,Time)) continue; <=== right here, i-1 when i=0 will be outside the Time[] array and crashes.

Not sure why they don't crash on you too?

Is there something I should be doing to get these indicators to work properly?

Thanks for your help !

profitabl

That happens when you add strict to that code(when you try to change that existing code)

When you use strict some additional array handling code must be added. Use them as is (without the strict addition or use the code that is already adjusted for a strict mode) and then there will be no problem at all

William Snyder
9493
William Snyder  

Replaced the Tema in the Sentiment zone oscillator(szo) with the one more average, if you leave ColorsOnSlope = false then you will have the szo to be colored on szo/avg signal cross.

sentiment_zone_oscillator_oma_nrp.mq4