iCustom Needs Enhancement

I have an iCustom up for enhancements:

http://i45.tinypic.com/2h7jx2b.jpg

It needs the following:

http://i46.tinypic.com/2hh2gwl.jpg


Basically, I need the indicator to output the Highest High and the Lowest Low, between the Range that is established by the Crossing of the indicator.

When the indicator's White Line crosses from above to below its Gray Line, the bars of the indicator turn Blue. When the indicator's White Line crosses from below to above its Gray Line, the bars of the indicator turn back to Yellow.

The period in which the indicator's bars are Blue, establishes the Range in which the Highest Price High and the Lowest Price Low, need to be output as Modes.

So, the Highest Price High within the Indicator's Blue Range would be Mode [0], and the Lowest Price Low within the Indicator's Blue Range would be Mode [1]. Highest Price High = Mode[0]. Lowest Price Low = Mode[1].

The last thing would be a graphical esthetic. Simply make the indicator print a horizontal line for Mode[0] and Mode[1]. Thus, each Mode (Highest Price High and Lowest Price Low) would have a horizontal line at their respective price levels.

I need to Modes to also be viewable in both the Tester Journal and the MT4 Experts tab, when the indicator is loaded into either a chart, or running inside an EA. So, basically, just enter Print() commands somewhere near the bottom of the indicator's code.

Anyone want to take a shot at doing this?

I posted this on another board as well and made an offer to that board. So, to be fair, I'll make the same offer here:

For the person who steps up and decides to make the enhancements, I'll toss in a Scalping Method that I use with the indicator as well. So, you get the indicator (which is one of the most important indicators you will ever see) and a light weight scalping methodology that I deploy with the indicator. It won't be the EA that I'm currently building, but at least the scalping method will give you some ideas about what can be done with the indicator.

This is a Magnitude Indicator and it is one of many Delta Class indicators that I created the concept for over the years. It is in fact the very first indicator I ever created and its very much like ATR - with a couple different twists.

Let me know, if you are able and willing to code the enhancements per spec.

Thanks. http://netdna2.forex-tsd.com/images/...ular_smile.gif

If you notice, the iCustom's crossing range ends one bar before the actual cross on the right side.

There is a reason for this - that was not a drawing error on my part. So, the iCustom Crossing Range needs to end one bar before the actual cross on the right side.

The bar that actually forms the right side cross, is the actual Trigger - and therefore, cannot be a component of the trigger logic. That is by design.

I'll explain the details of that to the one who decides to code the enhancement.

Cheerios!

I think I might have figured out a visual iteration that might work.

OpenBuy Progressive Fixed Length Scan:

O_Tac[0] > O_Sac[0] && O_Sac[1] > O_Tac[1] &&
O_Sac[2] > O_Tac[2] && O_Tac[3] > O_Sac[3] &&
Bid >= iHighest(Symbol(),PERIOD_H1,MODE_HIGH,2,2)
||
O_Tac[0] > O_Sac[0] && O_Sac[1] > O_Tac[1] &&
O_Sac[3] > O_Tac[3] && O_Tac[4] > O_Sac[4] &&
Bid >= iHighest(Symbol(),PERIOD_H1,MODE_HIGH,3,1)
||
O_Tac[0] > O_Sac[0] && O_Sac[1] > O_Tac[1] &&
O_Sac[4] > O_Tac[4] && O_Tac[5] > O_Sac[5] &&
Bid >= iHighest(Symbol(),PERIOD_H1,MODE_HIGH,4,1)
||
O_Tac[0] > O_Sac[0] && O_Sac[1] > O_Tac[1] &&
O_Sac[5] > O_Tac[5] && O_Tac[6] > O_Sac[6] &&
Bid >= iHighest(Symbol(),PERIOD_H1,MODE_HIGH,5,1)
||
...
...
...
O_Tac[0] > O_Sac[0] && O_Sac[1] > O_Tac[1] &&
O_Sac[12] > O_Tac[12] && O_Tac[13] > O_Sac[13] &&
Bid >= iHighest(Symbol(),PERIOD_H1,MODE_HIGH,12,1)


[inverse for OpenSell]

I think I'll set the maximum scan range to 20 hours. That should be enough to capture those periods when the iCustom range gets extended for a prolonged period of time, while still capturing the normal iCustom range periods.

I'll toss this iteration method into Excel as normal (just to make sure there are no typo propagation issues), extend it to 20 and then dump the method into the builder.

If this works, I'll post the results with a video showing the EA running. Until I get it working, the offer still stands:

I share this original prototype indicator, one (1) of the methods I use to trade it within a range of 81% to 99% accuracy to a specified scalp target and typically from 20 to 75+ pips per day; with the MQL developer who takes on the task and makes the deliverable per spec.

Beat me to the punch! I'm reaching for Excel now!

The above iteration method is wrong, wrong, wrong. All wrong. Its a good method, but it won't bake the pie I'm after.

I think I've figured out the new method. It will turn out to be a bit more complex (layered) but I believe it should work. I'll know more when I finish the model for it.

In the meantime, the offer still stands.

Maybe if you post your indi then you have a chance of getting it modified.