if ((RVI_m1 < 50) && (Mom_M1 > 100) && (cci_MM1 > 0)) { STR_m1 = "-";  color_M1 = Lime;}  // original
   if ((RVI_m1 < 50) && (Mom_M1 > 100) && (cci_MM1 < 0)) { STR_m1 = "-";  color_M1 = Silver;} // original
   if ((RVI_m1 < 50) && (Mom_M1 < 100) && (cci_MM1 > 0)) { STR_m1 = "-";  color_M1 = GreenYellow;}  
   if ((RVI_m1 < 50) && (Mom_M1 < 100) && (cci_MM1 < 0)) { STR_m1 = "-";  color_M1 = OrangeRed;}   
   
   
   if ((RVI_m1 > 50) && (Mom_M1 > 100) && (cci_MM1 < 0)) { STR_m1 = "-";  color_M1 = Orange;}  
   if ((RVI_m1 > 50) && (Mom_M1 > 100) && (cci_MM1 > 0)) { STR_m1 = "-";  color_M1 = Silver;}   
   if ((RVI_m1 > 50) && (Mom_M1 < 100) && (cci_MM1 < 0)) { STR_m1 = "-";  color_M1 = Orange;}  // original
   if ((RVI_m1 > 50) && (Mom_M1 < 100) && (cci_MM1 > 0)) { STR_m1 = "-";  color_M1 = Silver;}  // original

Attached Files

	_Signal_Bars_Meter.mq4 (24.0 KB, 236 views)
	_Signal_Bars_Spread.mq4 (16.4 KB, 224 views)

could it be CJA finally released his source code? (Signal_Bars_MFI)

you think "xMeter" approach more convenient 4 modifications than "SignalBars" approach?

Just wanted to take the time to say thanks for all the great work you share here fxbs. Anytime I see your name on a post I take the time to read it, it's always good. I hope you are enjoying some of the fruits of your hard work!
Hope you have a great New Year!!!!!

HS

[quote=highway3000;174052]
in such case (SigBarsMFI) if we do modifications - ethic wise we need to put note "based on..." or "mod. ..." or other which shows - initial version has been changed not by author and author not bare responsibility 4 changes if modified version go wrong (so other guys can feather develop original indi and make their own mistakes)

Thanks, HS!
i'm trying to.... we're developers - not competitors here; lets help each other and lets enjoy fruits of our work and HAVE A HAPPY NEW YEAR all of as

I don't know if CJA released the source code or not.

I just posted the TRO MULTI METERS



The code can be found in the signal bar thread.

The TRO MULTI METERS are built as "building blocks"... you can load multiple copies and stack them any way you like. You are NOT restricted by me as a programmer.

I think this is much more convenient than having to ask someone to change their code for you.

sure i know your is different - that's cool; and i see 4 working on MFI Bars you came back to TRO(xMeter) approach (blocks) - is one more convenient 4 modifications, debugging,etc. ) or it's just matter of habit?
not much playing with the objects, that's why i'm asking...

First, I am new to MT4 so I don't know all the tricks, tips and traps.

But since iMT4 is compiled code, I don't think you can pass functions as input parameters. In TradeStation, I can pass functions as parameters so I can write input driven code which give the user ultimate control.

So the building blocks approach is the next best thing. Rather than have all the code in one indicator, you have small, flexible indicators that can be loaded repeatedly. Then after you figure out exactly what you want, you can combine the code.

I wrote an ma indicator in the meter format that had a fast, medium and slow ma. But now, I wrote a single ma indicator that can be loaded multiple time. One person may want just 1 ma, another 3 and another 8. No need for me or anyone else to rewrite code.

You mentioned objects... I still have to learn objects.

hi

Anyone know of a MTF ZIgZag Pointer - ideally with the one that leaves the original arrow behind

Thanks