pdum_aiui

Appearance

Interface: InputReport ​

Defined in: telemetry.ts:478

The OTHER phase-1 question: are we getting every sample the browser has, and is that enough?

A coalescing ratio of 1.00 is meaningless on its own, and reading it as bad news is the trap this function exists to close. It means "one sample per event", which is:

  • a catastrophe if getCoalescedEvents() does not exist — the browser batched the pen's high-frequency samples and we had no way to ask for them;
  • a non-event if it does exist and returned one anyway — the browser had nothing to batch, because it was already delivering one event per sample. We are seeing everything there is. The rate is simply the rate.

Same number, opposite meanings. Only coalescedApi separates them.

Properties ​

canCoalesce ​

canCoalesce: boolean

Defined in: telemetry.ts:480

Can we reach PAST the browser's event rate to the pen's raw samples?

headline ​

headline: string

Defined in: telemetry.ts:485

The one-line banner.

level ​

level: "unknown" | "good" | "workable" | "poor"

Defined in: telemetry.ts:482

How much signal we are actually getting, judged against what a pen needs.

rateHz ​

rateHz: number

Defined in: telemetry.ts:483

says ​

says: string

Defined in: telemetry.ts:486