[aaa]

I've adapted MA Ribbon from EL 2 AB

http://www.traderslaboratory.com/for...html#post78174

How 2 plot a cloud between the 2 avgs and change color area when avg crosses ??

Here is my preliminary code

Plot(C,"Price",colorBlack,styleCandle);
	
Periods      = Param("Periods",      30, 2, 200, 1, 0 );
Displacement = Param("Displacement", 30, -150, 150 );

Plot( EMA( c, Periods ), "", 
	ParamColor( "ColorMM", colorBlue ), 
	ParamStyle( "StyleMM") | styleThick | styleNoRescale ); 

Plot( EMA( c, Periods ), "" , 
	ParamColor( "Color Delay", colorWhite ), 
	ParamStyle( "Style Delay") | styleNoRescale | styleNoLabel, Null, Null, Displacement  );

I've found this from ICHIMOKU

The problem is where 2 put Displacement ?

PlotOHLC(Span1,Span1,Span 2,Span2,"Cloud",colorWhit e ,styleCloud );

[Tams]

that's a nice looking chart...

[aaa]

Hi Tams

I shouls have precised that it's a snapshot from the Xcellent help...

It was 2 illustrate the ICHIMOKU stylecloud which is similar than your MA Ribbon

PlotOHLC(Span1,Span1,Span 2,Span2,"Cloud",colorWhit e ,styleCloud );

Oups....

[Head2k]

Use Ref function for displacement.

Plot( Ref( EMA( c, Periods ), Displacement), ...

Negative displacement moves the average in the past, positive displacement in the future.

Anyway, the whole code would be as follows:

Plot(C,"Price",colorBlack,styleCandle);
	
Periods      = Param("Periods",      30, 2, 200, 1 );
Displacement = Param("Displacement", 15, 0, 150, 1 );

EMAactual = EMA( c, Periods );
EMAdisp = Ref( EMA( c, Periods ), -Displacement);

Color = IIf( EMAactual > EMAdisp, colorGreen, colorRed);

PlotOHLC( EMAdisp , EMAactual, EMAdisp, EMAactual, "Cloud", Color, styleCloud);

Originally Posted by Tams »

that's a nice looking chart...

I admire people who can trade off flying carpets.

[Head2k]

Originally Posted by Head2k »

Negative displacement moves the average in the past, positive displacement in the future.

Sorry, actually it is the other way around. Negative displacement moves the past data into the future and positive displacement moves the future data into the past.
So with positive displacement you refer to future data which are not known in the actual moment, and that won't work in real time usage and it can screw up your back test.

That's why I allowed only for negative displacement in the code.

[aaa]

Hi Head2K

ThanX again 4 your help

Ref( formula ); is the key of the magic carpet 2 make it flying

Now 3 questions for a champion
------------------------------------------------

about else

ColorBuble =
IIf( Condition1, Color1,
IIf( Condition2, Color2,
IIf( Condition3, Color3,
IIf( Condition4, Color4,
ElseColor )))) ;

For each condition we must add a ) at the end
In this case I don't need the elseColor

But it works fine

Is there an other smartest way ?

------------------------------------------------

Negative displacement moves the average in the past, positive displacement in the future.

I've seen that the colors is 1 bar late than normally

How 2 avoid that ?

----------------------------------------------------------------------

I don't arrive to change the color of an avg when it changes trend

EL

if avg > avg[1] then
SetPlotColor[1](1, Line.upcolor);
else
SetPlotColor[1](1, Line.dncolor);

AFL

IIf( EMAactual < EMAactual[1] , colorYellow, colorBlue);

The problem is the [1] I think

[aaa]

I'm surprised to arrive to transpose "easily" code from EasyLanguage 2 AFL

I thought C is complicate but, for easy indicators I use, it is OK

May B AFL is the "EasyCLanguage" ?

[Head2k]

To the 1st question:
If you want the color to change in a discrete manner you can list the conditions just like you did.
If you want the color change continuously over the color spectrum, or if you can join your descrete conditions into a mathematical function, then you can use this function to define the color.
Then you can use ColorRGB function (find it in AFL help) to change the color. So you need to convert your conditions into mathematical functions which output values between 0 and 255 for red, green and blue.

To the 2nd question:
The color change doesn't happen late. If you zoom in you can see that the two averages cross usually somewhere in between of two bars. The color is defined by relation of the two averages at the last bar. Then the averages cross, but before the next bar is reached the color remains the same. Once the next bar is reached, the relation between the averages is re-examined and the color changes at that bar.
AmiBroker can't change color somewhere between bars, only at a bar.

To the 3rd question
IIf( EMAactual < EMAactual[1] , colorYellow, colorBlue);
This will always return colorBlue, because you compare EMAactual to EMAactual, that is two same numbers. So the expression in the condition is always false.

Originally Posted by aaa »

I'm surprised to arrive to transpose "easily" code from EasyLanguage 2 AFL

I thought C is complicate but, for easy indicators I use, it is OK

May B AFL is the "EasyCLanguage" ?

I can't judge this. I am not a programmer and I never learned C. I've learned just AFL from AmiBroker help.
When I was a 10 years old child I used to learn TurboPascal which was kind of an educational programing language, so I had an idea about what a loop is and so on. So the only thing I can say is that AFL is probably easy, because if one has some elementary knowledge of programing languages principles, then he/she can learn it very well only from the help included in AB.