does the current version of UniRenko bars type support the following:
1) New bar only when current bar is exceeded by 1 tick
2) No new bars on session start
---> Not sure
3) Filled gaps
The following 2 users say Thank You to justtrader for this post:
Thank You so much for coding this indicator. It is absolutely awesome! I've used it for the past few days and, it works perfectly on my uni-renko charts. It solves the only issue (in my opinion) that I was having on my uni-renko charts. It helps me see the price without having to rely on the price axis panel. Thanks Again, Great Job!
oh btw, it will also work on other chart types as well, (min, tick,other renko types, etc.. Although it only prints the current price, w/o the projections. All the way around it works great!
The following user says Thank You to Ricky H for this post:
Thanks for your reply. I see the code is not checking for Session start (unlike Renko in @BarsType.cs) but where do you see the 'New Bar When Exceeded' in the calculation ? Is it the hard inequality "</>" in lines 61/62 as opposed to ">=" and "<=" ?
thanks for your help !
Please register on futures.io to view futures trading content such as post attachment(s), image(s), and screenshot(s).
Funny you ask for it - I was thinking about this recently as with this change UniRenko would truly become universal (oh, ok plus some more like new session treatment, new bar on hit or exceed).
@mrmuggins version of UniRenko (screenshot from your journal) most likely uses a workaround that hardcodes some values, eg. Offset == 98 (or >=98) is considered as zero. This should work fine, but it is still a workaround for the fact that native Period.BarsPeriodValue is set to have minimum value of 1 (ie: Math.Max(1, value)).
I don't see a way to override this property to change its behaviour but maybe someone had achieved this.
Alternatively it would be also interesting to try adding completely new property and not relying on the existing Period.XXXXX fields.
Was anyone successful in any of these 2 tasks?
The following 2 users say Thank You to gregid for this post: