Here you go
The rest of the levels and the price are calculated relative to those bounding levels
The price you want to monitor is set by the PivotPriceoption. Shift is done by shifting hours (if required)
Updated version posted here : https://www.mql5.com/en/forum/general
That is so freakin! sweet! Mladen.
Sorry about the bad decription, but its probably for the best, because what you did here is a million times better than my limited ideas.
Big thanks, Mladen!!
I would like to ask you to fix/optimize the digital ASC indicators.
They are very slow and even crash MT4 and do not work on every broker for some reason.
I wonder whether they can be used in an EA?
I have a little request for you.
Is it possible to create an indicator that plots high and low of the first 4 hour daily range?
Also it would be perfect if candles will coloured as green when close >high of the 4 hour level high, red if close< 4hour level low and blue if in the range.
Hope it is clear and many thanks!
1. Can you be more specific : which one is the one that is causing crashes? As far as I know the "mesa" versions are slow but it will need some serious recoding in order to speed them up, but I can not know which one is causing crashes so it would be a great help if you can be specific about the one that causes those crashes (and are those crashes or it freezes your mt platform).
2. Also, there is definitely a problem with AscTrend indicators and it was known a long time ago. That was one of the main reasons why igorad did his work on LabTrend indicators (this thread : https://www.mql5.com/en/forum/178426 ) He did it in order to clean up the errors that AscTrend versions had and I am afraid that any indicator using AscTrend indicators is going to inherit problems they had and have
But for now, can you see if you can find out answer to questions in point 1
Yeah..that was not very encouraging...
Any indicator I posted causes MT to slow down dramatically.
I use a Athlon 64 X25 Dual and it is clear that this processor cannot handle these indis this way (100% usage).
Maybe they can be optimized in terms of processor usage?
The entropy histogram does not work at all.
The ordinary ASC indicators work fine on all platforms, though.
The problem is clearly the heavy calculations and as the author is not a professional MQL programmer, I believe better code can improve velocity.
I can not find "R-MESA_Cutoff_frequencies" indicator anywhere (it is called from some of those indicators). Do you have it?
Mladen is it possible to give the StepChart_v1-sperate indicator the ability to overlap over other indicators. For example Im trying to overlap it over a Histogram. Is that possible?