Thanks for additional averages and prices along with extra features.

do you means the original line is thin one but we have to consider thick line that formed with possible less lag but removing some tiny false signal on purpose "as a result" .

regards

mntiwana

No. The original corrected average was always the thick line. But the color of that line was determined by the cross of the underlying average (thin line) and the corrected average (the thick line) - I decided to add an option to have a color of the corrected average on slope, not just on those crosses

No. The original corrected average was always the thick line. But the color of that line was determined by the cross of the underlying average (thin line) and the corrected average (the thick line) - I decided to add an option to have a color of the corrected average on slope, not just on those crosses

Dearest MLADEN

Thanks for early response,understand exact ...... so the thin underlying line is of same average but with few faster periods only

if there any difference (code wise) in between corrected averages and your bundle package Averages (37) ..... or the only difference with extra underlying line that help change coloring (as an option) and capable removing few tiny signals along side a bit possible lag.

Thanks for early response,understand exact ...... so the thin underlying line is of same average but with few faster periods only

if there any difference (code wise) in between corrected averages and your bundle package Averages (37) ..... or the only difference with extra underlying line that help change coloring (as an option) and capable removing few tiny signals along side a bit possible lag.

regards

mntiwana

The thin line is the average (the same as in the averages indicator)

The thick line is the corrected average - that is that same average but "corrected" only if the change of the average exceeds the desired deviations amount (something similar to the "filters" we are using). Try setting the "number of deviations" to 0 and you shall see that you are going to get exactly the same value as the averages since in that case there is no correction that needs to be checked

The thin line is the average (the same as in the averages indicator)

The thick line is the corrected average - that is that same average but "corrected" only if the change of the average exceeds the desired deviations amount (something similar to the "filters" we are using). Try setting the "number of deviations" to 0 and you shall see that you are going to get exactly the same value as the averages since in that case there is no correction that needs to be checked

can the alerts be added to this masterpiece, Mladen?

This is the Volume Flow Indicator (original idea by Markos Katsanos), that was already made at this forum (one version posted here https://www.mql5.com/en/forum/180648/page961 for example), but this version is somewhat changed

The difference is that this version allows "pre-smoothing" - the idea was to check if the value can be smoother but without lag. It seems to be working OK (see the lower example for comparison - the difference is obvious), so I decided to post it here

mntiwana:Dearest MLADEN

Thanks for additional averages and prices along with extra features.

do you means the original line is thin one but we have to consider thick line that formed with possible less lag but removing some tiny false signal on purpose "as a result" .

regards

mntiwanaNo. The original corrected average was always the thick line. But the color of that line was determined by the cross of the underlying average (thin line) and the corrected average (the thick line) - I decided to add an option to have a color of the corrected average on slope, not just on those crosses

mladen:mntiwanaNo. The original corrected average was always the thick line. But the color of that line was determined by the cross of the underlying average (thin line) and the corrected average (the thick line) - I decided to add an option to have a color of the corrected average on slope, not just on those crosses

Dearest MLADEN

Thanks for early response,understand exact ...... so the thin underlying line is of same average but with few faster periods only

if there any difference (code wise) in between corrected averages and your bundle package Averages (37) ..... or the only difference with extra underlying line that help change coloring (as an option) and capable removing few tiny signals along side a bit possible lag.

regards

mntiwana:Dearest MLADEN

Thanks for early response,understand exact ...... so the thin underlying line is of same average but with few faster periods only

if there any difference (code wise) in between corrected averages and your bundle package Averages (37) ..... or the only difference with extra underlying line that help change coloring (as an option) and capable removing few tiny signals along side a bit possible lag.

regards

mntiwanaThe thin line is the average (the same as in the averages indicator)

The thick line is the corrected average - that is that same average but "corrected" only if the change of the average exceeds the desired deviations amount (something similar to the "filters" we are using). Try setting the "number of deviations" to 0 and you shall see that you are going to get exactly the same value as the averages since in that case there is no correction that needs to be checked

mladen:mntiwanaThe thin line is the average (the same as in the averages indicator)

The thick line is the corrected average - that is that same average but "corrected" only if the change of the average exceeds the desired deviations amount (something similar to the "filters" we are using). Try setting the "number of deviations" to 0 and you shall see that you are going to get exactly the same value as the averages since in that case there is no correction that needs to be checked

Fresh_Prince:can the alerts be added to this masterpiece, Mladen?

Fresh_PrinceHere is a version with alerts added

Files:This is the Volume Flow Indicator (original idea by Markos Katsanos), that was already made at this forum (one version posted here https://www.mql5.com/en/forum/180648/page961 for example), but this version is somewhat changed

The difference is that this version allows "pre-smoothing" - the idea was to check if the value can be smoother but without lag. It seems to be working OK (see the lower example for comparison - the difference is obvious), so I decided to post it here

Files:Sir ,

Pls can you add alert for colour change ?i i have disabled the cb colour . thanks

Files:pawanraghav:Sir ,

Pls can you add alert for colour change ?i i have disabled the cb colour . thanks

sir,

i have tested newer versions but those does not have kv input parameter.without kv ,other versions slightly differs in giving signals.pls mladen sir.

pawanraghav:sir,

i have tested newer versions but those does not have kv input parameter.without kv ,other versions slightly differs in giving signals.pls mladen sir.