MTF and Repainting

If you have been burned by a higher-timeframe indicator before, this is the page to read first. The global On Bar Close? toggle is the single highest-stakes decision you make with this indicator. It is a real tradeoff in both directions, the scope is every slot on the chart at once, and you should make the decision on purpose rather than by accident.

What repainting actually means here

"Repaint" gets used to describe many things, not all of them the same. Inside this indicator, repaint has one specific meaning: a slot's line moved on a past bar of the chart because the higher-timeframe data underneath it changed. On the Base trim, the only mechanism that can do that is the posture you chose for On Bar Close?.

A plain example. You are on a 1-minute chart with Slot 01 at 5 minutes and On Bar Close? OFF. The current 5-minute bar is still live. Slot 01 is reading the live 5-minute bar, so Slot 01's three lines reflect whatever the 5-minute close would be at this instant. One minute passes. The live 5-minute bar has moved. Slot 01's lines now reflect the new live reading, and because this all happens while the same 5-minute bar is still open, the line on your chart has shifted even though no higher-timeframe bar has closed. That is repainting in the specific sense this indicator can produce it.

What this indicator does not do is alter already-closed higher-timeframe bars. Once a higher-timeframe bar has closed, the slot's values for that closed bar do not move. Repaint, here, is confined to the window in which the current higher-timeframe bar is still open.

The two postures

There is one switch. On Bar Close? under the PU Settings group. ON by default.

ON. Every slot returns the previous confirmed higher-timeframe bar's values. The slot's lines step forward at the moment the slot's higher-timeframe bar closes and hold between closes. A slot at 60 minutes steps once an hour. The line you see on your chart at a given moment is the value that was true at the last completed higher-timeframe close. It will not change before the next close.

OFF. Every slot returns the live higher-timeframe bar's values. The slot's lines can shift on the current chart bar and continue shifting until the higher-timeframe bar itself closes. A slot at 60 minutes can drift in real time for up to an hour. The line you see is a live read, not a confirmed one.

The scope is the entire indicator. Flipping the switch changes the posture on Slot 01, Slot 02, and Slot 03 together. There is no per-slot override on this trim. If you need per-slot control — for example, you want Slot 01 live and Slot 03 confirmed — you are asking for a feature that lives on the CTX trim, and this page cannot pretend otherwise.

What each posture costs and what it buys

The honest way to read this tradeoff is to name both costs and both benefits in the same breath.

On Bar Close? ON.

• Costs: up to one higher-timeframe bar of latency. A slot at 60 minutes can be reporting a value as old as 59 minutes and change. When a clean reversal happens inside an hour on a 60-minute slot, ON will not see it until the hour closes.

• Buys: stability. The line you are looking at was true at a closed higher-timeframe bar. It will not walk on you between closes. If you act on it at one moment and look again thirty seconds later, the line is in the same place.

On Bar Close? OFF.

• Costs: live redraw inside the current higher-timeframe bar. The lines can — and will — move. Lines that looked decisive mid-bar can un-look-decisive before the bar closes. The alerts on this indicator still fire at chart bar close, and they can fire on an OFF-posture live read that then changes before the underlying higher-timeframe bar confirms.

• Buys: responsiveness. You see the live higher-timeframe picture evolving. In exchange for accepting that the picture is not settled until the bar closes, you avoid waiting a full higher-timeframe bar for the slot to update.

Neither posture is universally better. They are a tradeoff. "OFF is faster" is a half-sentence; the full sentence is "OFF is faster and redraw-exposed across every slot at once on this trim."

Verification drill

The fastest way to internalize the difference is to watch it happen once.

1. 1-minute chart of a reasonably liquid symbol. Default slots. On Bar Close? ON.

2. Eyes on the Slot 01 teal lines. Wait out one full 5-minute bar. The teal lines hold and then step at the 5-minute close in one event.

3. Flip On Bar Close? OFF. Wait out one full 5-minute bar. The teal lines now drift through the 5-minute window; they can move on every 1-minute tick the 5-minute bar takes. They will settle at the 5-minute close but not before.

4. Flip back to ON.

While you are watching, notice that Slot 02 and Slot 03 are behaving the same way as Slot 01 — the toggle flipped them all. If you only expected Slot 01 to drift, that is a quiet reminder that the switch is global on this trim.

When each posture is the right answer

Some honest guidance on the tradeoff, in plain language:

• ON is appropriate whenever you act on a slot's value. If the line is going to change your decision, use the confirmed posture. The cost is latency; the benefit is that what you saw is what the indicator will show next time you look.

• OFF is appropriate when you are watching a higher-timeframe picture develop and you understand the higher-timeframe bar has not closed. "Watching" is different from "acting on." OFF is also fine when a slot's timeframe is short enough that one higher-timeframe bar of latency is a meaningful lag on the workflow you are doing.

• OFF is not a speed upgrade. It is a different posture with a different cost. Flipping OFF because a chart "looks slow" without registering what that costs across three slots at once is a specific misuse.

If you find yourself considering OFF for only one slot — because, say, only the 60-minute slot has the latency you mind — the Base trim cannot give you that. Either accept ON across the board or switch to the CTX trim, which exposes per-slot repaint control.

One more frame that is worth carrying. The honest question is not "is the posture I have set correct?" The honest question is "does the way I am reading the chart require a confirmed higher-timeframe value, or can it tolerate a live one?" Those are different questions, and the second one often has a different answer for different parts of the same process. Context-scanning tolerates a live read because you are forming a picture, not pulling a trigger. Position entry usually does not tolerate a live read because you are committing to the value you saw. Stops and exits live somewhere in between, depending on how tightly they are tied to a specific band or basis value. Under the Base trim's single global toggle, you are implicitly choosing one answer for all of those situations at once. If that tradeoff does not match your process, it is a clean prompt to move to the CTX trim rather than a reason to flip the switch mid-session and hope.

The slot-timeframe guard

There is a second multi-timeframe safety behaviour on this indicator that deserves naming alongside the repaint toggle: the slot-timeframe guard.

A slot cannot run on a timeframe lower than the chart timeframe. If you set Slot 01's TimeFrame: to 30S on a 1-minute chart, the indicator will fire a runtime error and stop rendering. TradingView surfaces this in the status bar; the error names the offending slot, so you can tell immediately which input to fix.

This is a guard, not a failure. Running a slot on a lower timeframe than the chart timeframe is not a meaningful multi-timeframe read — it would require the indicator to look at sub-bar history that is not actually available at chart resolution, or to pretend a resampled value is the lower-timeframe value, both of which would be a quiet lie. Refusing the configuration is the correct move.

The fix is always to raise the slot's timeframe to at or above the chart timeframe. The indicator will render again as soon as the guard passes.

Why the global switch is global

The short version: on the Base trim, this is one of the design boundaries that keeps the trim Base. A per-slot toggle multiplies the surface — every slot grows a repaint toggle in the inputs dialog, every piece of teaching has to cover the per-slot case, and every reader has to reason about which slots are in which posture. The CTX trim accepts that surface expansion; the Base trim deliberately does not.

That is also why this page cannot treat the Base trim as a diminished CTX. The Base trim's scope is three slots, one global toggle, and the Lite moving-average library. When a reader's workflow requires per-slot control, that is a prompt to switch trims, not a prompt to work around a limitation.

Interaction with alerts

Every alert this indicator fires is gated by the close of the chart bar. That is a consistent rule under both postures.

Under ON, the alert reads a slot value that is already confirmed on the higher-timeframe side. The reported condition is firmly on closed ground.

Under OFF, the alert still fires at chart bar close, but the slot value underneath the alert may still have been a live higher-timeframe read. That means an alert can fire reporting, say, a blended uptrend, while one of the contributing slots was reading a higher-timeframe bar that had not yet closed. The alert is honest about what held at chart bar close; it is not honest — nor is it trying to be — about whether the higher-timeframe side was itself confirmed.

See Alerts for the full list of alerts and the gating behaviour written out there.

A short comparison frame

If you need per-slot repaint control or cross-ticker behaviour, the CTX trim is the right tool. If three slots with one global posture is what you want, you are already on the right trim — and the one switch above is, from this point on, a decision you make on purpose.