Thank you, @LittleCaro:

I’ve been informed by PM about discrepancies regarding my indicator on chart vs. inside backtester, called by iCustom(). Seems to be perfect on chart, but problematic in backtester.

Everybody interested, please check this and report back.

s.

That’s correct:

You’re pointing out the same detail I discussed with G. by PM: 3-bit vs. 4-bit logic. If you refer to my code:

enum CLEAR_STATE {
CLEAR_NONE,            // undefined condition
CLEAR_BULL,            // bullish condition
CLEAR_BEAR            // bearish condition
};

you will see my ‘clear’ preference for 3-bit, just…[Read more]

Thanks Lowphat, will test it. About your test result comparison, may i know it was on whice pair, time frame and begin to end time period of testing ? May be the result i got because of my bad historical data preparation? I download tick data from dukascopy using tickstory, convert it to HST format with gmt shift 0 or +2 (helsinki time) for my 2…[Read more]

Yep:

I stepped in the same (at least similar) trap in my first attempt to code this! My latest version is absolutely simple, with no parameter at all.

s.

I’m afraid there’s some misunderstanding here. As far as I got it, V. does NOT talk about replacing all iCustom indicator calls by functions calls to mqh libs. It’s all about proper code management. Please trust him.

@VlanFx: please trust yourself and your expertise and do what you know to be right!

Re. iCustom() calls pro’s and con’s (we had…[Read more]

Absolutely correct! In the end we will have several mqh-libs, each serving a specific purpose. These will be glued together by the main program. Code maintenance and enhancement will be much easier that way!

When counting code lines, the largest project I was involved was several million lines for an investment bank. We…[Read more]

My simplified Clear Method Indicator, as requested. My clear method mqh lib is included in the mq4 file for convenience.

Buffer 0: output = 1 for bullish, else 0
Buffer 1: output = 1 for bearish, else 0

No input parameters, so iCustom() should be rather simple:
double iCustom(
string symbol, // symbol
int…[Read more]

Not too bad, if you have no or only minimum experience in coding mq4!

I did not check the function yet, but looks ok at first sight.

What you should change in any case is adding indentation, function headers, etc: give your code a meaningful structure! I would suggest to read this post of mine, load the software and apply it to a copy…[Read more]

@simplex & @anti,

It is ok … thanks

Could anybody  provide a little more technical detail, maybe a link to a site where this topic is covered?

s.

Thanks for pointing this out! The forum software changes names of uploaded files from time to time. Better to place them in zip containers.

s.

@smallcat:

Ask @Anti – this is his baby!

s.

@Lowphat : May i know what do you mean with “anomalies” ? Could you please explain it ? Did you test the indicator via strategy tester, and check the “visual” option to see how the indicator works on history data (and in realtime too) ? Thanks

Very nice and clear steps bro   i like to use for instead if while too (i always forget to add i++ or i–, increment or decrement at the end of the while loops, so it is always looping and freeze my mt4).   And if you don’t mind, i would like to see the whole code of this … thanks in advance.

Just did a back test on EA penguin 1.2 by VlanFx. Tested on EU H4 from 2010-06-30 to 2015-12-11 with spread of 1.5 pips, result is great
Thanks to GG53 and all of you guys ….

Absolutely correct – that’s it! The highest warning level of this indicator will be dumped in a black hole without a warning.

Who wants that?

s.

Edit: Adding #property strict is always the first thing I do before compiling downloaded code. All those hidden little sins of fellow coders displayed as compiler errors and warnings. Ok -…[Read more]

Absolutely correct – that’s it! The highest warning level of this indicator will be dumped in a black hole without a warning.

Who wants that?

s.

Ok:

(a) A loop over those m bars is exactly the thing to do first. I would prefer a for () { … } in this case, others might go for a while () { … } . What I like with for loops: the basic loop control is on top, I see it at a glance. (b) Inverting those negative ranges would imply to check for sign first and then multiply by -1. Easier to…[Read more]

Thanks a lot G … and thanks for the great link too
Wow, so many great developments here and at main thread … thanks guys

Edit: ( delete. Content and links is already provided by simplex. Sorry ).

Thanks a lot G … and thanks for the great link too
Wow, so many great developments here and at main thread … thanks guys

Edit:
Found short pdf @FF …[Read more]