Distant mappings need an explicit pointer or highlight

What it is

Invert lives in a photo editor’s top bar; the selected layer thumbnail lives in a right rail. The layout will not let the button move next to the layer. Once proximity has given up the mapping, a second channel has to draw it: light the object, or pull a visible line. That is explicit pointing — repairing “what does this change?” after distance has failed.

Longer copy is not the repair. The row flushing red while Delete is held, the histogram range lighting as a price slider moves, the canvas shape stroking when a layer name is tapped — those are pointers.

Why it happens

Highlights and leader lines work because both ends enter a unique state at once. Vision binds them by common fate, not by location. That is a substitute channel after proximity has failed, and it spends contrast, so it has to be brief and state-bound: alive only for the life of this action.

The substitute has a time window. The highlight must appear before or during the press — a flash after the request returns lands on a gaze that has already left. Leader lines have a density ceiling: a screen full of connectors points at no pair in particular. Touch has no stable hover, so a pointer that exists only on hover is simply absent.

Studying it

Borrow brushing and linking from visualisation: act in one view, test whether the matching mark in another view can be found. Compare “data changes, appearance does not” against “the object is highlighted in sync”.

Independent variables: presence of a synced highlight, timing (before / during / after the action), whether the object is still in the viewport. Dependent variables: rate of correctly naming the affected object, time from action to locating it, false attributions to unrelated objects.

In the lab the highlight is often the only change on screen. In a product it competes with badges, toasts and motion, so detection has to be measured under that noise.

Where it stops holding

If the object is off-screen, a highlight is a non-event — scroll it into view, or park a thumbnail beside the control. Fill-only red highlights vanish in greyscale and for many colour-vision deficiencies; strokes and marks survive. When the two ends already sit together, a leader line steals contrast the content needed. Touch and stylus have no reliable hover; the pointer has to fire on press, or live as a persistent selection stroke.

Applying it

• On the frame the control is focused or held, change the object’s appearance (stroke, veil, row wash). Do not wait for the network.
• When the ends sit on different screens, use a leader, a rubber-band, or a thumbnail beside the control — not a longer label on the button.
• Drop the highlight the moment the action ends, or it becomes a coat of paint.
• How to check: mask the UI so only the control is visible (or crop the screenshot to the toolbar) and ask “which region on this screen will change?” If the object cannot be named, the pointer was never built.

Related

• Same group: F1.01.1 Distance between a control and its object decides whether the mapping can be inferred · F1.01.3 When one control acts on many objects, the scope must be marked
• Nearby: D1.03 Selection and highlight · F1.08 Overlay anchoring
• Search terms: explicit pointing · brushing and linking · leader line · visual linking