Nearby fingers can be merged into a single reported contact

What it is

If two fingers land closer than the controller can separate, their capacitive blobs join and the system emits one identifier and one coordinate. The user planted two fingers; the event stream contains a singleton. That is contact merging. It is not a full slot table dropping a finger: slots are often still free, and the segmentation simply read two peaks as one.

Why it happens

Electrode pitch sets spatial resolution. If neighboring capacitive peaks lack a deep enough valley, connected-component labeling emits a single blob. Wet skin, thick films, and large contact area widen the peaks, shallow the valley, and make merges likelier. Firmware often refuses a new id below a minimum peak distance. The merged coordinate is usually a weighted centroid of both fingers, sitting in the empty glass between them—hitting neither control under a finger, nor the point the user aimed at. Children’s shorter fingers and stronger closing habit merge a gesture that separates on an adult hand.

Studying it

With calibrated finger sleeves or two conductive probes, open a millimetre-scale gap from closed to apart and record the distance at which id count goes from 1 to 2. Independent variables include contact area, screen region (center versus edge), humidity, and gloves. Dependent measures are the merge threshold, how far the reported coordinate sits from the two-finger midpoint during the merge, and how long the merge lasts. Human fingers repeat poorly; probes give a geometric floor, then remeasure a natural thumb–index pinch for an ecological spacing.

Where it stops holding

An active stylus plus a finger usually travel different recognition channels and will not collapse into one id. Infrared frames and optical touch merge when occlusion projections overlap; millimetre figures from capacitive panels do not transfer. A deliberate knuckle or pad press is a single blob by construction, not a merge. Games that stack two fingers as a “heavy strike” are using the merge on purpose; a firmware update that raises resolution turns that chord into two ordinary taps.

Applying it

• For gestures that need a stable pair, seed the landing farther apart than the device’s merge threshold, with visible anchors or an animation that separates then closes.
• Measure the merge gap on the target device with probes or a ruler and put that number in the gesture spec; do not accept “it looks like two fingers.”
• Do not pack two single-finger controls so close that only a pair can reach them; a merged centroid lands in the seam and lights neither.

Related

• Same group: C2.19.2 Merged contacts disable pinch gestures at onset · C2.19.3 Contact splitting can produce a sudden coordinate jump · C2.19.4 Split thresholds depend on sensor precision and contact area
• Nearby: C2.01 Finger contact area and touch centroid · C2.18 Multitouch contact limits
• Search terms: contact merging · blob segmentation · multitouch resolution