Support Board
Date/Time: Thu, 13 Nov 2025 07:56:18 +0000
Post From: Question on Zig Zag codes for alert conditions
| [2025-09-29 12:20:30] |
| LongShortz - Posts: 26 |
|
Thanks. I found that after I submitted the ticket and was able to get that working. But still having trouble. It seems that current calculations change the calculus for the entire sheet. I'm looking to be able to keep my signals on the screen indefinitely once they've triggered for more effective back testing. Basically, I want the sheet and the chart to reflect what was real at that point in time. But what I'm finding is: (assume bullish for example) ** I have two zig zags. One is a higher range than the other. I'm looking for the lower range to confirm the higher range with confluences to fire a signal ** 1. Price moves up off of a higher low and exceeds the higher range threshold which locks in that we're going to have a new HH 2. From there we get a pullback that does NOT exceed the threshold but is now throwing a 'temporary' HH code even though it isn't confirmed. So if I want to confirm the HL, I have to look back to the second most recent value. 3. At this point the lower range is confirming a HL which matches the higher range HL. With confluence, the signal fires. 4. Now price moves up breaking the previous 'temporary' HH which moves the HH to a point later in time than my signal candle. In doing so, the second most recent value I was basing the signal on is now the most recent value which completely breaks the logic and the signal is erased. But that wasn't the condition in real time. So therein lies the question. Is there a setting or formula modification or something else that could prevent this from happening? |