Directional pen gestures turn selection into one continuous action
Aliases: directional pen gesture · stroke command · directional mark
What it is
A directional pen gesture encodes a command in the heading of one stroke (up, down, diagonal, rebound), collapsing “open menu → move to item → confirm” into one continuous down–stroke–up. Selection is no longer a tap on a rectangle; it is a directed mark. That is not the same path as ink kept as content: the command stroke is interpreted on lift and vanishes or becomes feedback; content ink stays as writing or drawing.
Why it happens
A pen is good at short directed motion and poor at stopping on a small button. Direction lays command space onto angle: eight ways already hold frequent actions; a polyline or two-segment mark can grow the set. The motor structure is one ballistic act—the start names the object (this item, this selection), the heading names the verb (delete, duplicate, drill in). With no mid-flight rectangle to hit, time goes to planning the movement, not visual search, and experts can mark without looking at a menu. The cost is angular resolution: hurried marks land in the wrong sector, so dead zones and confirmation (the upcoming command name revealed along the stroke) are required. Versus a click menu, directional marks replace Fitts-style terminal aiming with start-point aiming plus heading classification; the start is usually the already-fixated object, which is where the pen is.
Studying it
Implement the same commands as a click menu and as directional marks. Measure novices following labels, experts from memory, and the practice curve between.
Independent variables: number of directions (4/8/12), in-flight labels, whether polylines are allowed. Dependent measures: time, sector errors, whether the eyes leave the object, whether practiced time approaches one short stroke.
Timing only after the mapping is memorized overstates the method; learning and adjacent-sector confusion must be included.
Where it stops holding
Once the set exceeds headings people can mark cleanly, errors jump; nest a second segment rather than packing the circle. Directional marks cannot be the default input where they collide with handwriting. People sitting opposite see reversed directions; demos and shared screens mislead. A finger can also mark a heading, but without hover preview and nib precision, starts on fine objects are worse.
Applying it
- Bind frequent, object-tied verbs to directional marks; keep rare or destructive actions on a confirming menu.
- Show the command that will fire during the stroke; commit on lift; leave dead zones between neighbours.
- Cap the first-layer direction count; extra commands use a second segment, not a twelve-way split.
- How to check: novices mark once with labels, then from memory after a delay; count sector errors and looks at the menu. The same object with a click menu as control; practiced marks should approach one short stroke, start still on the object.