Crossing-based interface¶

A graphical interface in which moving a pointer across a target boundary triggers an action.

Version: v2 · 2026-09-19 · History
Domain-specific #: 3978
Domain group: Professional & Organizational Practice
Origin domain: Human-Computer Interaction (HCI)

Core Idea¶

Crossing can complement pointing, and activation depends on boundary, direction, trajectory and state rather than merely entering or clicking inside a target. The system monitors a cursor path for a qualifying boundary intersection and dispatches the command bound to that crossing event. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

The load-bearing residual is not the broad topic of human computer interaction. It is the domain-specific identity fixed by the input device and pointer, target and boundary geometry, qualifying direction and trajectory, activation state, feedback, command, error handling and performance measure are explicit.

How would you explain it like I'm…

Swipe Across the Line

On most computers, you point at a button and click it. In a Crossing-based interface, you make something happen by sliding the pointer across a line instead, like running through a finish-line ribbon. Which way you cross can matter too.

Cross a Line, Not Click a Button

Most computer screens make you move the pointer onto a button and click. A crossing-based interface works differently: you trigger a command by moving the pointer across an edge or line on the screen. What counts can depend on which line you cross, which direction you go, and the path you take. The computer watches the pointer's path and, when it crosses the right line the right way, does the action linked to it. This can be used alongside normal pointing and clicking.

Boundary-Crossing Command Activation

A Crossing-based interface activates commands when the pointer's path crosses a boundary, rather than when the pointer merely enters a target or clicks inside it. The system continuously tracks the cursor's trajectory, detects when it intersects a qualifying boundary, and triggers the command linked to that crossing. Whether a crossing counts can depend on the boundary's shape, the direction of crossing, the path taken, and the current state of the interface. Crossing can complement pointing rather than replace it. Describing such an interface properly means stating the input device, the target and its boundary geometry, what direction and path count, the activation state, the feedback, the command, how errors are handled, and how performance is measured.

A Crossing-based interface is an interaction technique in which a command is triggered by the pointer trajectory intersecting a qualifying boundary, rather than by entering or clicking within a target region. The system monitors the cursor path for boundary intersections and dispatches the command bound to a qualifying crossing event. Qualification depends on boundary geometry, crossing direction, trajectory, and interface state, so the same line may be inert or active depending on how and when it is crossed. Crossing is typically positioned as a complement to pointing, offering a different selection primitive with its own performance characteristics. A precise specification makes explicit the input device and pointer, the target and boundary geometry, the qualifying direction and trajectory, the activation state, the feedback, the bound command, error handling for unintended crossings, and the performance measure used to evaluate it. The concept is narrower than HCI in general: it names this boundary-crossing activation model, not every gesture or pointer interaction.

Scope of Application¶

Crossing-based interface belongs to human computer interaction and is useful where the analyst can specify the typed human computer interaction carrier, including objects, relations, parameters, conventions, evidence, and comparison cases, then evaluate the input device and pointer, target and boundary geometry, qualifying direction and trajectory, activation state, feedback, command, error handling and performance measure are explicit. The scope is broad within that domain but bounded by the need for the input device and pointer, target and boundary geometry, qualifying direction and trajectory, activation state, feedback, command, error handling and performance measure are explicit. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.

Clarity¶

The abstraction clarifies a crowded vocabulary by making the input device and pointer, target and boundary geometry, qualifying direction and trajectory, activation state, feedback, command, error handling and performance measure are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name Crossing-based interface can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated.

Manages Complexity¶

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Crossing-based interface. Crossing-based interface compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning¶

Identify the carrier. State what the elements, states, objects, or observations are: the typed human computer interaction carrier, including objects, relations, parameters, conventions, evidence, and comparison cases. Reject examples whose alleged carrier belongs to a different problem.
Lock the constitutive rule. Express the input device and pointer, target and boundary geometry, qualifying direction and trajectory, activation state, feedback, command, error handling and performance measure are explicit independently of one notation or implementation.

Knowledge Transfer¶

Knowledge transfers strongly among subfields of human computer interaction because they reuse the typed human computer interaction carrier, including objects, relations, parameters, conventions, evidence, and comparison cases, The system monitors a cursor path for a qualifying boundary intersection and dispatches the command bound to that crossing event., and type the carrier, state every parameter and convention in the definition, test that the input device and pointer, target and boundary geometry, qualifying direction and trajectory, activation state, feedback, command, error handling and performance measure are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions¶

Current abstraction Crossing-based interface Domain-specific

Parents (1) — outgoing typed relations

Crossing-based interface is a kind of Affordance Prime

It remains its own entry because its identity is fixed by the input device and pointer, target and boundary geometry, qualifying direction and trajectory, activation state, feedback, command, error handling and performance measure.

Hierarchy path (1) — routes to 1 parentless root

Crossing-based interface → is a kind of Affordance

Neighborhood in Abstraction Space¶

Crossing-based interface sits in a crowded region of the domain-specific corpus (5^th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Interface & Interaction Design Methods (20 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-25