Both form a bullish engulfing.
The long bullish candle of pattern 1 shows me that bulls have strengthened. Its body engulfs the previous two bodies and…[Read more]

Thanks a lot for this post and post #11279, very good and clear explanation … Easy to understand the reason 

And the code formatting works well, including the indent.

Thank you very much Simplex … 

Thanks a lot for this post and post #11279, very good and clear explanation … Easy to understand the reason 

And the code formatting works well, including the indent.

Thank you very much Simplex … 

Maybe try to change your view on our community project for a short while: consider we’re not only coding one EA, but a collection of flexible and exchangeable trading software modules instead. The overall goal of these modules should be to facilitate coding an EA, and the EAs which are the result of our…[Read more]

At the moment only in my brain or on my hard disk. I will post my version later this morning. Stay tuned, please!

s.

It’s not a trick, it’s just a bit of coding work using the OnTimer() event handler. If you’re interested, refer to my experimental indicator posted here. That one does not paint candles of timeframes below one minute, but it visualizes tick data in a different way. Compiling that data to candles and displaying them would be a simple step.

s.

G.

This is not what I meant – I coded the ALMA in mq4 a long time ago. What I meant is whether anybody has tried to apply an FIR filter like ALMA to the VZO algorithm instead of the EMA (IIR).

s.

This is not really true. You can calculate values for lower timeframes than shown on chart without any problem. You just can’t visualize those numbers in the way we are used to when looking at MT4 indicators.

Most simple case: the same timeframe on chart and on indicator (red volume histogram on my pic). We’re used to display a…[Read more]

Ask @Anti – this is his baby!

s.

Thank you very much, @MTH2014 (Kiads), @smallcat, and @simplex! Will try it next night …

Thank you very much, @MTH2014 (Kiads), @Smallcat, and @simplex! Will try it next night …

There is no “5” variable there…

Attached pls find how it should look like on EURJPY, H4.

For the EA purpose an Histogram is also Ok.

The ForexGT_VolumeOsc is an added feature to Pin-point exact bar entry, but for the current version it’s not required since we enter on Peak/Trough area…[Read more]

There is no “5” variable there…

Attached pls find how it should look like on EURJPY, H4.

G.

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

There is no “5” variable there…

G.

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

There is no “5” variable there…

G.

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.

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]

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]

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]

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]

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]

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]

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.

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]

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]

Right.

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

Right.

G.

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

Hi @smallcat

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

tankhang

That’s not quite correct. A plain FIR filter has got a static set of filter coefficients. What you’ve put on the table in your drawing looks like something adaptive or self-adjusting. That’s another kind of story.

It can be done with FIR filters, but might be simpler using an IIR filter as a basis.

The plain concept is explained…[Read more]

That’s not quite correct. A plain FIR filter has got a static set of filter coefficients. What you’ve put on the table in your drawing looks like something adaptive or self-adjusting. That’s another kind of story.

It can be done with FIR filters, but might be simpler using an IIR filter as a basis.

The plain concept is explained…[Read more]

You can use some kind of second order Low-Pass filter.

G.

“…A new high is made (in an uptrend) or a new low (in a downtrend)…”

G.

I didn’t use your actual code (only the skeleton for painting the arrows). My kernel code is different from yours:

I didn’t used your actual code. My kernel code is

The logic in that version is Wrong, so do not use it. I will upload the newer one soon, today or tomorrow …