Logic follows guidelines as in post ##9553.

There is no “5” variable there…

G.

https://www.mql5.com/en/charts/4378801/eurjpy-x-h4-atom8-financial-services

Logic follows guidelines as in post ##9553.

There is no “5” variable there…

G.

Thanks bro.

@smallcat

highest low: watch all 5 lows in your interval, choose the highest one (the highest among the lows)
lowest high: watch all 5 highs in your interval, choose the lowest one (the lowest among the highs)

This is the common interpretation. I don’t think that G. follows a different one.

s.

@smallcat: since build 600 we can have up to 256 buffers in an mt4 indicator. Early this year I coded an indicator that used about 50 buffers for internal precalculations. The memory and cpu consumption was horrible at first. Then I reconsidered: do I really need all those bars on my charts? I limited it to 20000 maximum bars per chart, loaded the…[Read more]

@smallcat:

In an indicator, there’s no need to shift buffers manually. The terminal engine does that automatically. Only of you declare arrays which are no buffers you have to care for that yourself.

Did you read the articles I linked to?

In Sergey’s book chapter, scroll down, search for IndicatorCounted – it’s essential to understand those…[Read more]

Use IndicatorCounted() function in order to calculate only relevant bars. It’s fast and easy on the CPU.

G.

Thanks for that information G …

That factor 100 will simply transform a simple relation (a-b) / (a + b) for easier reading, that’s all: for a = 4 and b = 1 you will get 60.0 instead of 0.6. Simple scaling for convenience. Your code in general: avoid variable names that say nothing, like buffer1 or buffSix. If you’re using meaningful nam…[Read more]

@smallcat:

That factor 100 will simply transform a simple relation (a-b) / (a + b) for easier reading, that’s all: for a = 4 and b = 1 you will get 60.0 instead of 0.6. Simple scaling for convenience.

Your code in general: avoid variable names that say nothing, like buffer1 or buffSix. If you’re using meaningful names like volumeBullish and…[Read more]

@smallcat:

That factor 100 will simply transform a simple relation (a-b) / (a + b) for easier reading, that’s all: for a = 4 and b = 1 you will get 60.0 instead of 0.6. Simple scaling for convenience.

Your code in general: avoid variable names that say nothing, like buffer1 or buffSix. If you’re using meaningful names like volumeBullish and…[Read more]

@smallcat:

That factor 100 will simply transform a simple relation (a-b) / (a + b) for easier reading, that’s all: for a = 4 and b = 1 you will get 60.0 instead of 0.6. Simple scaling for convenience.

Your code in general: avoid variable names that say nothing, like buffer1 or buffSix. If you’re using meaningful names like volumeBullish and…[Read more]

Hi guys!

A short advice for all unexperienced coders. When writing an indicator, you usually want to achieve 2 basic goals, no matter which calculation the indicator will perform:

When loading initially, the indicator should calculate and display its values for a certain number of bars or for all bars on chart, if possible.
After that, the…[Read more]

Hi @smallcat,

I found this one. It’s a bit older and I don’t know whether it works on latest R / MT4 builds. Also some sample code in that thread.

s.

Thanks a lot bro, trying to create one is a good idea …

@smallcat: right place? Well, yes and no!

Yes, because this thread is intended to discuss this kind of questions.

And no, because I don’t have the source code of Gadi_TickVolume_v2.2, so I do not know what’s happening inside. That’s the general problem if you don’t have the mq4 source: you can only guess and in many cases the result will be…[Read more]

@smallcat: right place? Well, yes and no!

Yes, because this thread is intended to discuss this kind of questions.

And no, because I don’t have the source code of Gadi_TickVolume_v2.2, so I do not know what’s happening inside. That’s the general problem if you don’t have the mq4 source: you can only guess and in many cases the result will be…[Read more]

Hi G, Does it mean you get only the big ratio ? Lets say > 70% or >80% ? [/quote] Hi @smallcat If I am not mistaken, GG53 is replacing the volume become ((Close-Open)/(High-Low))*volume in the volume oscillator algorithm.. tankhang [/quote]

Right.

My “logic” was that the volume is spread between Low & High, but its true contribution to the mo…[Read more]

Hi G, Does it mean you get only the big ratio ? Lets say > 70% or >80% ? [/quote] Hi @smallcat If I am not mistaken, GG53 is replacing the volume become ((Close-Open)/(High-Low))*volume in the volume oscillator algorithm.. tankhang [/quote]

Right.

G.

Hi G, Does it mean you get only the big ratio ? Lets say > 70% or >80% ? [/quote] Hi @smallcat If I am not mistaken, GG53 is replacing the volume become ((Close-Open)/(High-Low))*volume in the volume oscillator algorithm.. tankhang [/quote]

Ou thanks mate, i have missed understood the word “ratio” … now it is clear.

Hi G, Does it mean you get only the big ratio ? Lets say > 70% or >80% ? [/quote]

Hi @smallcat

If I am not mistaken, GG53 is replacing the volume become ((Close-Open)/(High-Low))*volume in the volume oscillator algorithm..

tankhang