Skip to content

Event Handling

The ziviDomeLive constructor registers Processing keyEvent and mouseEvent hooks. The built-in ControlP5 panel remains facade-owned and does not expose its events through Scene.

Implement callbacks on the scene:

public void keyEvent(processing.event.KeyEvent event) {}
public void mouseEvent(processing.event.MouseEvent event) {}

Do not add main-sketch forwarding such as ziviDome.keyEvent(event). That delivers the same event twice.

Service-aware scenes can map stable action names instead of branching in the raw callback:

services.actions().bindKeyPressed("reload", 'R', services::requestReload);
services.actions().register("reset-camera", () -> services.camera().orbit().reset());
services.actions().trigger("reset-camera");

The runtime dispatches action bindings before the raw scene callback. The raw callback still runs, so avoid performing the same operation in both paths. Bindings are cleared automatically when the scene leaves ownership.

Global Shortcuts

  • h: toggle the built-in panel
  • m: cycle the configured preview view
  • Left/Right arrows: previous/next scene

Global shortcuts are processed by the facade without requiring sketch forwarding.

Camera Input

When setSceneCameraInputEnabled(true) or services.camera().setInputEnabled(true) is active, navigation gestures reach the scene-space OrbitCamera instead of the independent Standard perspective camera. This prevents one drag or wheel event from moving two cameras at once.

All registered callbacks are removed during terminal disposal.