Dave Skender

Thanks for the info. I’ll take a closer look at `depth` when I get around to this one. Just an FYI to everyone, TradingView is not always a reliable standard...

> Can we include the "Last Extend Bar" option in the ZigZag indicator? We do extend the line to the most recent bar already, are you just interested in having...

> > We do extend the line to the most recent bar already, are you just interested in having the "H" value? > > Yes sir. Would an `IsBullish` `bool`...

I still have a lot of uncertainty how `depth` might negatively impact the quality of this indicator. It doesn’t smell right. I can try to explain. What I hear is...

And now I’ll eat my words. You can’t chain ALMA to ZIG ZAG, it needs a full quote! 😵‍💫 I can update Zig Zag to allow this chaining option, but...

@anthonypuppo I think has the best lead here. If I understood it correctly, he’s saying a reversal point also has to be a [Williams Fractal](https://dotnet.stockindicators.dev/indicators/Fractal/#content), where `depth` is the `windowSpan`...

> Can we please solve it? I’d love to, but can’t quite figure out a simple way to make future candle dates align with what’s expected or accurate. Any ideas?

The bigger vexing problem is not determining the values and actual number of future bars, but rather the actual accurate dates for them. You can imagine all the time scenarios...

Until we get to implement the right thing, I’m locking this thread to avoid splitting our discussion, for now, please respond and comment to poll #1060.

The only way to really know if it’s accurate is to calculate it manually and compare. I have both [code example](https://github.com/DaveSkender/Stock.Indicators/blob/8dd8e7578a1f755cf1bf247ff15858605cccd95f/src/m-r/Macd/Macd.Series.cs) in C#, the underlying algo for that Python package,...