Touch And Mobile Controls

Touch-oriented views use the same graph, renderer, and behavior APIs as desktop views. A few options tell Helios how much of the touch interaction surface it should own and how the interface behavior should classify compact layouts.

Custom behaviors are for app-specific logic that needs lifecycle, state, subscriptions, or coordination with built-in behaviors. They are not required for small scripts, but they are useful when a feature should attach and detach cleanly.

Configure Touch Interaction

suppressBrowserGestures tells Helios that the canvas should own gestures such as pan and pinch inside the visualization area. The interface behavior options configure compact-state thresholds, while hover options show how behavior tuning can remain declarative.

Configure Touch Interaction

Body Header

Render Console

Register A Custom Behavior

This custom behavior selects the first few nodes when it attaches. The important detail is that it composes with the default behavior namespace: custom code uses context.helios.behavior.selection instead of duplicating selection state.

Register A Custom Behavior

Body Header

Render Console