There is drawing problem if the data feed is interupted (disconnected, pc goes into suspense mode, etc).
Considering the main logic is taken from rlc32, I suspect the bug also exists on rlc32.
Anyway, its not fixed yet. A helping hand will be really appreciated.
i guess ea is different with indi. on ea, delayed ticks are submitted to start() one by one, but with indi, it only submitted the last one.
will dwell the code again...
Unfortunately, rlc32 doesn't draw a Renko chart, it draws something closer to range bars and tries to make it look like Renko. Renko charts use CLOSING PRICE, rlc32 is constantly monitoring the BID price and drawing a bar the instant the block size is reached. That's not a Renko chart. A real Renko chart would only be checking once per bar (i.e. at the close) and adding the appropriate number of "bricks". It's possible to add multiple bricks at once.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
RenkoShade2 - Draws Renko boxes in normal TF:
Author: refi