Multi Timeframe Indicators - page 140

homestudy
196
homestudy  

Thanks fxbs

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

fxbs
3203
fxbs  

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)

fxbs
3203
fxbs  
homestudy:
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

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

fxbs
3203
fxbs  

CJA, Thank You 4 your NEW YEAR Gift to this Forum!

TheRumpledOne
2181
TheRumpledOne  
fxbs:
could it be CJA finally released his source code? (Signal_Bars_MFI) you think "xMeter" approach more convenient 4 modifications than "SignalBars" approach?

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.

fxbs
3203
fxbs  

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...

TheRumpledOne
2181
TheRumpledOne  
fxbs:
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.

Nordic12
99
Nordic12  

MTF ZigZag Pointer

hi

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

Thanks

fxbs
3203
fxbs  

Stochastic_Color_v1.02classicB.mq4 Mladen's Stoch. Mod

extern int KPeriod = 14;

extern int Slowing = 3;

extern int DPeriod = 3;

extern int MAMethod = 2;

extern int PriceField = 0;

extern int overBought = 80;

extern int overSold = 20;

extern string timeFrame = "Current TF";

extern string note_timeFrames = "M1;5,15,30,60\H1;H4;D1;W1;MN||0-CurrentTF";

extern bool showBars = false; // Bars as Sidebar(overlay) - drop in any sep.window

extern int BarsLevel = 5; //BarsLevel 0-100

extern int BarsSize = 2; //0-5

extern bool showArrows = true;

extern color ArrowUpClr = LimeGreen;

extern color ArrowDnClr = Red;

extern int ArrowSize = 1;

extern bool alertsOn = false;

extern bool alertsMessage = true;

extern bool alertsSound = false;

extern bool alertsEmail = false;

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

+ Unic#generator (thanks Mladen)

string MakeUniqueName(string first, string rest)

{

string result = first+(MathRand()%1001)+rest;

while (WindowFind(result)>= 0)

result = first+(MathRand()%1001)+rest;

return(result);

}

Happy New Year!

TheRumpledOne
2181
TheRumpledOne  

Latest updates to the TRO MULTI METERS.

Thanks to a couple of fellow codes, I got the object delete problem solved.

Files: