Button placement must avoid the natural finger-rest zone during writing, to prevent accidental firing

What it is

If a barrel button sits on the stretch where the index finger or thumb already rests while writing, it will be pressed every few strokes. Accidental firing switches tools, pops a menu, or starts erasing, which looks like the software changing mode at random. Placement is hardware ergonomics: clever debounce is weaker than moving the key off the rest band.

Why it happens

In common grips (tripod, quad), the index pulp sits about a third of the way up the barrel from the nib, the thumb a little higher on the opposite side. A button in that band sees the normal component of writing force as a click. If travel and force are designed as a light “definite press”, rest force already fires; if they are heavy, an intentional press wrecks the grip. Flush keys snag less than proud ones but are harder to find on purpose, so some designs are both flush and light—the worst pair. A rotationally symmetric barrel lets the button roll into the rest band; a flat or anti-roll section can park it outside (usually higher and off to the side). Software debounce and “counts only while in contact” catch some cases, not a latched switch from continuous rest. Handedness and children’s smaller hands shift the band; a single “xx mm from the nib” is not enough.

Studying it

Give people with several grips (tripod, low grip, left hand) a pen with adjustable or different button sites, write for fifteen minutes, and log unintentional presses. Use a pressure film or button telemetry to separate rest force from intentional press.

Independent variables: distance and phase of the button relative to the nib (under index / off index), prominence and force threshold, presence of an anti-roll section. Dependent measures: unintentional fires, success of intentional presses, whether grip changes to dodge the button.

A demo that says “try not to press it” undercounts; measure when attention is on the task.

Where it stops holding

Tap-only use (pen as a pointer, UI only) uses the rest band less, so the button can sit lower. A user-relocatable button pushes the problem onto people and still needs a factory site safe for most grips. If software treats accidental fires as user actions, logs will not show the problem.

Applying it

• Put the button above or behind the rest band, with an anti-roll section so it cannot rotate under the index finger.
• Set force above stable rest force and require a definite travel; do not put a latch on a flush, light key.
• Accidental fires should be immediately undoable and must not bind high-cost commands such as clear page.
• How to check: write a long passage naturally, telemeter the button, code unintentional fires from video. Repeat with left hand and a lower grip. An intentional task (hold to erase) must still be reachable; hiding the button to dodge accidents cannot make it unpressable.

Related

• Same group: C5.10.1 Barrel buttons map to tool switch or menu · C5.10.2 The eraser end is recognised by flipping the pen · C5.10.4 Button bindings differ by app, with no shared convention
• Adjacent: C5.13 Paper Feel, Friction, and Writing Haptics · C5.04 Palm Rejection
• Search: accidental button press · grip zone · barrel placement