I don't understand the problem with Support/Resistance lines. I don't mean the angled thing (there is no good way of getting rid of it), but rather what the problem described in your March 19 post is.
TD Sequential Ultimate
- Thread starter Enivid
- Start date
- Watchers 8
OK. Let's speak about TD Buy Setup, because Sell is a mirror.
Let's assume each bar 1-9 has high lower --> high of bar "1" creates TDST resistance. Obvious and script works fine
If any bar except 1 has high, which is the highest price in TD Setup - the high creates TDST resistance, as below
In case if close of bar before TD Setup has close which is the highest from any bar of TD Setup ---> this close price should be TDST resistnace. Examples marked in yellow:
Hope this clarifies TDST support/resistance
Let's assume each bar 1-9 has high lower --> high of bar "1" creates TDST resistance. Obvious and script works fine
If any bar except 1 has high, which is the highest price in TD Setup - the high creates TDST resistance, as below
In case if close of bar before TD Setup has close which is the highest from any bar of TD Setup ---> this close price should be TDST resistnace. Examples marked in yellow:
Hope this clarifies TDST support/resistance
Version 1.02 of TD Sequential Ultimate has been just released. It fixes numerous issues reported by @kris82wt and implements a limit variable for the number of bars used in calculation. Please download and test. The updated indicator is also available via our GitHub repository.
Version 1.03 of TD Sequential Ultimate has been released to fix an bug with old Countdowns being removed even when they shouldn't be removed.
It is an open source indicator, so yes, you can get it. Either from the indicator's page or from its GitHub repository.
I had to change Time[i+1] to Time i to make arrow draw on bar 9. Maybe Time always last reported finished candle.
Last edited:
The Setup Perfection arrow shouldn't necessarily appear on the 9th bar. It may appear on any bar starting from bar #8. Please see DeMark's article on this.
I know about it and I could see it repeatedly missed with one bar both on buy and sell setup.
Maybe Time(i) is always last reported finished candle. Then you need not use Time[i+1].
Last edited:
It never checks the current (unfinished) candle. The cycle never runs to bar #0:
MQL4:
for (int i = limit; i > 0; i--)
PS: Could you please show a screenshot of what you are trying to fix?
Also it seem to miss the perfected setup sometimes. On the buy setup here it should have been postponed.
Post automatically merged:
Yes, wait a minute.
This it what the same section looks like with the Time[i+1]. Before I changed.
And here is another example.
I'm looking at this code:
// Check perfecting:
// Setup candle #8:
if ((Low[i + 1] < Setup_Buy_6_Low) && (Low[i + 1] < Setup_Buy_7_Low))
{
Setup_Buy_Perfected = true;
Setup_Buy_Needs_Perfecting = false;
Perfection[i + 1] = 1;
PutCount(COUNT_TYPE_BUY_PERFECTION, "233", Time[i + 1], High[i + 1]); // Arrow up.
if (AlertOnPerfecting) DoAlert(i + 1, ALERT_TYPE_PERFECTING_BUY);
}
// Countdown can also start on this candle but farther in the code.
and I changed this line:
PutCount(COUNT_TYPE_BUY_PERFECTION, "233", Time[i + 1], High[i + 1]); // Arrow up.
to
PutCount(COUNT_TYPE_BUY_PERFECTION, "233", Time[i ], High[i + 1]); // Arrow up.
and also the other setup for sell.
Last edited:
Similar threads
