Feature 05

Clicks, and what they change.

Clicks are seen in the picture itself, beside what changed on screen at the same moment.

  • The pointer on three screens
  • Presses and their effects
  • One timeline
Synthetic test session · confirmed examples only
  • What happens

    The pointer is followed on all three screens. A press is seen from the picture alone, and reported beside what changed at the same moment: a page, a button, a dialog.

  • What SM1 records

    • The mouse button going down and up, with screen and place
    • Effects at the same moment: a page changed, a button pressed
    • All of it on the same timeline as the process
  • Why it matters

    An operator’s actions and their effects, on one record with the process: for shift reports and incident reviews. An input that changes no pixel cannot be seen.

In the scene API

Inputs and their effects.

The newest inputs and effects on the third screen (screens are numbered from 0).

Plain HTTP and JSON, on the device beside the screens. The film shows the same requests, with the answers SM1 gave in that session.

GET /api/events?kind=input,effect&screen=2&limit=8

[{"kind": "input",  "input": "down", …},
 {"kind": "input",  "input": "up", …},
 {"kind": "effect", "effect": "page_change", …},
 {"kind": "effect", "effect": "press", …}]

Pilot programme

Your screens, as data.

Tell us about your control room: how many screens, which systems, and what you would like to know from them. Contact us to join our pilot programme.