Gaze points; another modality commits
Aliases: MAGIC pointing · gaze pointing · multimodal gaze
What it is
Gaze-plus-confirm splits two jobs that usually tangle: gaze only indicates the object (moves a cursor, sets focus, previews), and commit is given to another modality—a mouse button, trackpad tap, controller trigger, pinch, space bar, spoken phrase. MAGIC pointing by Zhai, Morimoto, and Ihde is an early form of this split: gaze warps the pointer nearby, and the hand still does fine aiming and the click. It is not dwell selection, where commit is still a time integral, and not look-to-select, where commit is still a look.
Why it happens
The eyes are good at putting the fovea on an object of interest quickly, and bad at declaring “I take responsibility for this object”—that sentence needs a switch browsing does not pollute. Switches from hand, finger, or voice rest in the off state: no press, no pinch, no speech, no command. Gaze rests in the on state: it keeps looking. The combination uses that asymmetry: the fast channel points, the default-off channel commits.
The split also redirects error. Spatial error in gaze only affects which region receives focus; the commit can still make a small correction near the landing (MAGIC’s manual refinement) or trust the landing entirely (some VR pinch-on-gaze designs). Either way, false positives change from “looked at the wrong thing” to “looked at the right thing but did not press,” and browsing is released.
Studying it
Contrast pure gaze dwell, pure manual pointing, and gaze-point plus manual commit on two-dimensional acquisition, menu selection, and VR object picking, measuring time, error, and rated Midas feel. Independent variables include confirmator type (key, pinch, voice), whether gaze warps the cursor, and whether manual refinement is allowed. The original MAGIC pointing paper is this contrast. Report pointing time and commit time separately, or the combination only looks “about as fast.” Also record whether the confirmator pulls gaze off the target—that claim belongs on another leaf, but the design must let it occur or the combination’s real cost is invisible.
Where it stops holding
With no second modality available, the combination does not exist: someone with high tetraplegia and no speech may still have only dwell. If the second modality is slow (cloud speech) or noisy (a phrase in a loud room), commit becomes slower than pointing and the advantage is eaten. In some cultures or settings people cannot speak or raise a hand; social acceptability vetoes a technically faster confirmator. When calibration is poor, gaze pointing lands on the wrong object, and a clean commit still commits the wrong object.
Applying it
- By default let gaze move focus or preview, and commit with a default-off modality; do not bind both to the same look.
- On devices with manual refinement, allow a small correction of the landing before commit; on a headset that only pinches, make targets large enough to absorb gaze error.
- Verify by comparing look-only, hand-only, and gaze-plus-confirm for time and false commits, and confirm that reading labels does not issue commands.
Related
- Same group: C8.04.2 Decoupling pointing from commit can solve both speed and false activation · C8.04.3 The commit action must not shift the gaze point
- Adjacent: C8.02 Dwell selection · C8.03 Midas touch in eye input · C1.01 Types and properties of pointing devices
- Search:
gaze-plus-confirm·MAGIC pointing·gaze pointing