I agree that the "change" in post #35 should be used with caution. I have seen previous versions of the beta crash with that change (seems ok in current B15). Of course that means NT7 may still have issues. The problem is NT does not officially support it, so when you have an issue they are not going to fix it.
The other reason I would be careful is that you potentially get different bars every day you load data if you do not reset at the session boundary. Generally this is not too big a deal, but when you are backtesting you may get different results if you do not use a fixed set of dates. Even day to day, if you go back and look at your trades on a chart, the bars may be different than when you actually entered a trade. By resetting at the session boundary, it does not matter what day you start on, the bars will be the same.
I dont think there is a right answer in how to handle this part of bar creation, and it should be left to the user as a user preference (some platforms have this option).
The following user says Thank You to aslan for this post:
Please see attached screen shot indicating weird behavior of MedianRenko_NT7. I know that Roonius does not support MedianRenko (not even in NT6.5) and I think the guy who ported it to NT7 did say use with caution - but I am one of the ones that thought it worked fine until I saw the attached screen - so I thought I should warn against it.
I know some people may want to apply the fixes applied to SBSrenko to MedianRenko - but I think there may be other issues as well.
I noticed that Roonius SbSRenko conversion also works a lot more efficiently ...... on SbS v1 my CPU fan was working very hard on 2t chart where as now it runs and reloads with an ease .... thanks again to Roonius ......