Support Board
Date/Time: Sun, 22 Dec 2024 08:15:33 +0000
Post From: Reopen question re: Zig-Zag Bug in calculation Mode 3
[2015-04-13 23:43:13] |
User68474 - Posts: 201 |
When I last asked about the blatant bug in Zig-Zag Mode 3 using Setting "LAST" for "Input Data for High/Low", you replied most emphatically: "We cannot change this. This is just how it is. This study is immensely complicated as it is and we are certainly not going to complicate it further by trying to support this. We would not even consider it. Also when you are using the Last and not the High/Low you are going to have inconsistencies with this study between real-time updating and a full recalculation and we cannot help with those. " The error/bug which I was pointing out only occurs when the setting option "Calculate New Values on Bar Close" is checked "No". Does that dovetail with the second part of your answer to me re: real-time updating vs. a full recalculation? If I HAVE checked "No", when I see that the error has occurred (i.e. has not ended a swing at a bar's close/Last), I quickly go to "Studies" and simply hit "Apply" (without needing to open up the Zig-Zag settings). That temporarily corrects the problem, but, of course, only until the next swing. My goal is to be able to see the accumulating Volume with the "Display Zig-Zag Volume" checked "Yes". That is most helpful in anticipating what the total accumulated volume might be, not only for the present, ongoing swing, but also for the potential first bar of the next opposing swing IF/when, in fact, the criteria from Calculation Mode 3 are fulfilled. It's too bad that the one, seemingly small final step to make the study accurate (i.e. using "Last" for "Input Data for High/Low" and "Calculating New Values on Bar Close--No") is "too complicated", even for Sierra Charts. You say: "We cannot change this. This is just how it is". It does not see to me that there is a need to "change" anything. "How it is" currently DOES offer/allow the option of simultaneously having "No" checked on "Calculate New Values on Bar Close" and using "Last" for "Input Data for High/Low". The only "change" would be to have it work accurately. |