hmos-multidevice-interaction-methods

Use the onClick event, which handles both touch taps and mouse left-clicks, and inspect event.sourceType (SourceType.TouchScreen or SourceType.Mouse) to distinguish the input source. For context menus, bindContextMenu with ResponseType.LongPress and ResponseType.RightClick unifies long-press and right-click.

Set focusable(true) and use tabIndex for Tab-key order, or nextFocus with up/down/left/right component ids for arrow-key navigation. Customize focus appearance with the focusBox property or by tracking onFocus/onBlur state to change styles.

In the onTouch callback, check event.sourceTool === SourceTool.Pen to distinguish stylus from finger touch, then read event.touches[0].pressure (range [0,1)) to adjust stroke width. Use canIUse('SystemCapability.Stylus.Handwrite') to verify device support first.

Yes, ArkUI provides the hoverEffect attribute with Highlight, Scale, and None options, plus the onHover callback for fully custom hover styles. These apply when a mouse or trackpad is connected to tablets, 2-in-1 devices, or PCs.

Common causes include reading pressure without checking sourceTool is Pen, not handling undefined pressure values, or the device lacking stylus capability. Verify support with canIUse('SystemCapability.Stylus.Handwrite') and guard pressure reads before computing line width.

Skip unification when a page targets only a single input method, such as a pure touch phone app with no mouse or keyboard attachment. The skill also excludes pure visual animation tuning and business-flow changes unrelated to input methods.