regarding the pre-trading conditions: FFCal -> @Emonts contacted me by PM and sent me a mqh file for this with example on how to call the functions. Now he’s fixing it so it works with prefix/postfix pairs. So this one is covered. Max. Spread -> I’ll implement this one Trading Hours, TradeOnMonday, TradeOnFriday, FridayClose -> @slicken had imp…[Read more]

regarding the pre-trading conditions: FFCal -> @Emonts contacted me by PM and sent me a mqh file for this with example on how to call the functions. Now he’s fixing it so it works with prefix/postfix pairs. So this one is covered. Max. Spread -> I’ll implement this one Trading Hours, TradeOnMonday, TradeOnFriday, FridayClose -> @slicken had imp…[Read more]

Wish you merry Christmas, Happy Holidays and a Happy New Year!!

G.

Thanks slicken,

I’ll check it out during weekend.

Thanks,

G.

This is our MAIN indie, so it deserve its place here, untill concluded and we can agree on stable indicator.

In the meantime, someone can finalize the other pre-trading conditions functions (FFCAL, Hours, Spread, etc…).

G.

This is our MAIN indie, so it deserve its place here, untill concluded and we can agree on stable indicator.

In the meantime, someone can finalize the other pre-trading conditions functions (FFCA, Hours, Spread, etc…).

G.

Oooops…

Just saw that simplex beat me in the M1 testing issue…

G.

What about testing the EA in rorward test (demo account), with iCustom call on M1 for an hour or so?

This should give an answer to the “repainting” issue AFTER bar close.

G.

Yes, the initial requirement was TWO functions, one for PEAK and one for TROUGH. Hence the requirement for returning Peak()==1 and Trough()==1.

Now we are using (I hope…) just one function for both Peak&Trough, so the differentiation is redundant, and we can use 1, -1, 0 (or 3-bit logic…).

G.

Yes, the initial requirement was TWO functions, one for PEAK and one for TROUGH. Hence the requirement for returning Peak()==1 and Trough()==1.

Now we are using (I hope…) just one function for both Peak&Trough, so the differentiation is redundant, and we can use 1, -1, 0.

G.

Entry is by Peak/Trough breakout signal, regardless of bar type.

G.

Trade Entry point:

Currently we enter pending trade AFTER bar close.

If so, why enter on the High+xx (for LONG) or Low-xx (for SHORT)?

We can enter a Buy-Stop at the Close+xx (Long) or Sell-Stop at Close-xx (Short).

We can also enter Buy-Limit at the Close-xx or Sell-Limit at Close+xx, to get some extra pips.

(or even BOTH, as KIAD…[Read more]

Trade Entry point:

Currently we enter pending trade AFTER bar close.

If so, why enter on the High+xx (for LONG) or Low-xx (for SHORT)?

We can enter a Buy-Stop at the Close+xx (Long) or Sell-Stop at Close-xx (Short).

We can also enter Buy-Limit at the Close-xx or Sell-Limit at Close-xx.

(or even BOTH, as KIAD suggested…)

G.

Entry point:

Currently we enter pending trade AFTER bar close.

If so, why enter on the High+xx (for LONG) or Low-xx (for SHORT)?

We can enter a Buy-Stop at the Close+xx (Long) or Sell-Stop at Close-xx (Short).

We can also enter Buy-Limit at the Close-xx or Sell-Limit at Close-xx.

(or even BOTH, as KIAD suggested…)

G.

You decide which version of the Peak&Trough to use.

Once decided, I prefer the iCustom call to external indicator in initial development, and later on, once stabilized, convert it to MQH.

Make the decision among yourself based on actual results – and ignore my preference.

Let’s move on with a conclusion on this.

G.

If you read my posts on the subject: I’m all in favor for MQH file in the FINAL version.

For the timebeeing I prefer iCustom calling of the external indicator, for easy debugging and visualization.

iCustom doesn’t add lines of code, because the indicator is a separate, stand-alone, MQ4 file.

Furthermore, that indicator can be used, monitored,…[Read more]

What I see on chart is a Relative-Currency-Strength, which can benefit the current EA in several ways.

It can be used as a scanner to select which currency-pairs to trade, and in which direction.

It can also be used as a confirmation to the main logic.

Both of the above features are more than welcome to this thread EA.

G.

How does that indicator perform whithin the EA?

G.

I don’t know how many times is needed to request the use of iCustom ….

I already stated that the Peak&Trogh function needs completion before moving on, but instead we get more and more “logic” features and additions.

This is good, and I’m not against it, but lets focus on completing the MAIN logic first !!

G.

I don’t know how many times is needed to request the use of iCustom ….

I already stated the the Peak&Trogh function needs completion before moving on, but instead we get more and more “logic” features and additions.

This is good, and I’m not against it, but lets focus on completing the MAIN logic first !!

G.