Thanks for clarifying:

Depends on the logic. Just wanted to be sure. From decades of IT development, I have some experience with incomplete or ambiguous requirements specifications. IMO, it makes sense to ask if you’re not sure what your communication partner intended.

s.

G:

Do you mean a function that just displays the adaptive TP relative to the current bar, or a function setting an adaptive TP in relation to a given entry price, thus monitoring a certain trade?

s.

Here you are:

Place mqh file in the include folder.

Have fun testing, and any feedback welcome!

s.

Yes:

… and the original article written by Waleed Aly Khalil over here tells even more (quote from the abstract):

The main idea of the VZO was to try to change the OBV to look like an oscillator rather than an indicator

s.

I have it:

Will post it later after some code cleaning.

s.

Yes, you are right simplex. So, if  High==Low, it means there is no Volume, right ? So, we just don’t care about this candle …. or we take the previous one ? Any idea ?

Yep, this is obviously true:

IMO, the really interesting question is: how does the else if branch look like? You can exclude division by zero easily by some standard code, but you’ll have to make an individual decision what should be done after the case happened.

s.

Yep, this is abviously true:

IMO, the really interesting question is: how does the else if branch look like? You can exclude division by zero easily by some standard code, but you’ll have to make an individual decision what should be done after the case happened.

s.

Thanks for commission information G

Thanks brother. I just think like this :

MathPow(High – Low, -1)

does it means same as :

 1 / (High – Low)

So, it is actually a division operation … if i am not wrong …    but i could be wrong though …

Hi all,

I got this line of code from other thread :

double V = ( MathAbs(Open – Close) * MathPow(High – Low, -1) ) * Volume;

Just want to make sure about zero devide. If the result of (High-Low)==0.0, then the equation MathPow(High-Low, -1)  will cause error. Is it right?

@pipatronic :  Thanks for info about Obv Div.   

Hi all,

I got this line of code from other thread :

double V = ( MathAbs(Open – Close) * MathPow(High – Low, -1) ) * Volume;

Just want to make sure about zero devide. If the result of (High-Low)==0.0, then the equation MathPow(High-Low, -1)  will cause error. Is it right?

Welcome mate. I haven’t tested v 1.3 yet (will test it soon), but as you know some other features are not implemented yet in this version . But looking at your result (although it is still getting some loss), yes it is promissing. I am sure after all requirements are fullfill (peak trough, osc, trend, etc), we will see a much better result. Try…[Read more]

Hi @VlanFx:

I’m currently reviewing version 1.3 of the EA. In function CalcLot() you have the following line of code:

actualRisk = (100 * minLot * StopLoss * pipValue) / AccountBalance();

That variable actualRisk is never used thereafter. Is it reserved for some future use?

s.

1) will need big space (using many different file name, although we can delete it later, but that is extra work)

2) ==

3) may be can reduce conflict of read⁄write in number 2)

4) i think should be ok … the master process can be changed⁄replace by slave process after master’s job is finish (a slave becomes a master process if nee…[Read more]

My version 1.0 of Volume Zone Oscillator. It consists of a simple indicator file, and an mqh-library which should be placed in the include folder.

In final and practical EA use, there will only be one line of code required:

varName = iiVZO(symb, tf, vzoPeriod, shift);

For debugging and optimizing the EA, a simple iCustom() call of the indicator…[Read more]

My version 1.0 of Volume Zone Oscillator. It consists of a simple indicator file, and an mqh-library which should be placed in the include folder.

In final and practical EA use, there will only be one line of code required:

varName = iiVZO(symb, tf, vzoPeriod, shift);

For debugging and optimizing the EA, a simple iCustom() call of the indicator…[Read more]