Xeroforex wrote:

RJo wrote: Now... I understand "upward" to mean previous pivot < current pivot, and "downward" to mean the opposite--so this is how the condtions are coded.

Ahhhh I was struggling with that, but thought that it was the DP movement.

Attached for anyone interested is a visual representation of some rules of CoolCalms very fine system, thanks to all who contribute, and it's great to see Alorente here, he is a very insightful trader

Cheers...Ted

RJo wrote: I see we're already setting TradeorAlert to true, so let's do this on demo only. There is a fixed lot size input for each set of conditions that can trigger a trade. They are numbered as follows: S_Symbol_LS_0, S_Symbol_LS_1, etc. (toward the end of the list). S is Sell. B is Buy. ClosePositionsNonTH means: if you UseTradingHours, then all open positions will be closed at the expiration of those hours.

Xeroforex wrote:

RJo wrote: Now... I understand "upward" to mean previous pivot < current pivot, and "downward" to mean the opposite--so this is how the condtions are coded.

Ahhhh I was struggling with that, but thought that it was the DP movement.

Attached for anyone interested is a visual representation of some rules of CoolCalms very fine system, thanks to all who contribute, and it's great to see Alorente here, he is a very insightful trader

Cheers...Ted

RJo wrote:

coolncalm wrote: the code update.

CC

Just to confirm... by margin, you do mean free margin as in the figure shown by default in Empty4, correct?

coolncalm wrote:

RJo wrote:

coolncalm wrote: the code update.

CC

Just to confirm... by margin, you do mean free margin as in the figure shown by default in Empty4, correct?

Not that margin, actually. I meant a pip margin from the FastTMALine that will allow the EA to still trigger if all the other conditions are met but price only comes near the Fast line without touching/crossing it. You see, prices may not always touch/cross the Fast line before turning. From my little understanding of the present code (please correct me if I'm wrong!), if the price gets to say, within 5pips from the Fast line, meets all the conditions for entry but turns without touching or crossing the line which is the primary condition, the trade will not trigger. A margin of 10pips around the Fast line would have allowed the trade in the example to trigger. This allows us to better represent what i meant by "Price is at/near/below the lower FastTMALine".

What do you think? I'm no coder, so can only make suggestions when it comes to coding

RJo wrote:
V1b and v1c on Post 1, page 4 are updated with the following trading conditions:

iLow(Symbol(),0,1) <= ((iCustom(Symbol(),0,"FastTMALine for EA",2,0) ) + (FastPipBuffer*Point) || iCustom(Symbol(),0,"FastTMALine for EA",2,0) - (FastPipBuffer*Point)) ...for buy alerts, and

iHigh(Symbol(),0,1) >= ((iCustom(Symbol(),0,"FastTMALine for EA",1,0) ) + (FastPipBuffer*Point) || iCustom(Symbol(),0,"FastTMALine for EA",1,0) - (FastPipBuffer*Point)) ...for sell alerts.

FastPipBuffer is the new input. Defauts to 10. Please advise re any errors found.

alorente wrote:Quote: "Spotting a high TF high/low that can cause a new emerging bias while trading a lower TF can be tough. If the SEMA4X alert (or any indy) can be made to signal it on any TF (maybe with different colours depending on where a high/low occurred e.g. D1 - red, H4 - orange) it will help make lower TF trading safer. For now, I check high TFs manually for SEMA4X high/low alerts & adjust my trading accordingly".

I agree with you. Having an MTF Semaphor appear on the H1 chart with the color of the TF that triggered it, would be invaluable for consistent entries, without having to check other charts. I suggest making the Semaphor the same color as the TMA bands of that particular TF:

H1 Semaphor= Dark Orange.

H4 Semaphor= Magenta.

D1 Semaphor= Cyan.

If two or three Semaphors trigger on the same H1 bar (for example H4 and D1), it would be nice to have them appear one above the other or overlapping.