Crossing-based interface¶

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

Version: v1 · 2026-09-08 · History
Domain-specific #: 3978
Origin domain: human computer interaction
Subdomain: human computer interaction

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.

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. 2. 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) — more general patterns this builds on

Crossing-based interface is a kind of Affordance Prime

The proposed strict upward parent is prime:affordance.

Hierarchy path (1) — routes to 1 parentless root

Crossing-based interface → Affordance

Neighborhood in Abstraction Space¶

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

Family — Human–Computer Interaction & Interface Design (24 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08