a0b69f8cc7
Template tests / tests (push) Successful in 1m50s
Implements the architecture change from ai_prompts/prompt3.md: - New app/click-frames.js: shared timestamped frame ring + strict click-to-frame pairing (never a frame whose grab started after the click); legacy slack behavior kept behind capture.strictClickFrames=false. - New stream capture backend (app/stream-backend.js + hidden worker window): per-display desktop media streams sampled into ring buffers and PNG-encoded entirely off the main process, so click delivery is never starved by capture work. Auto-degrades to the legacy in-process frame loop when streams cannot start or the worker stops answering. - Clicks are paired with their frame at event time (eager pairing in enqueueClickCapture); only the storing is serialized, so slow encodes cannot skew later clicks in a fast burst. - Linux watcher: restored event-time root coordinates from xinput test-xi2 and merge raw/regular twin events structurally. - Replaced the 40ms time debounce with source-aware duplicate suppression: fast legitimate clicks are never dropped. - New app/coords.js: physical-to-DIP conversion with multi-monitor and scale-factor handling; Windows keeps screenToDipPoint. - STEPFORGE_CLICK_SELFTEST end-to-end hook: 3/3 clicks become steps via the stream backend with 0.00% marker offset on this host. - Tests rewritten/added: strict selection, coords, stream backend, Linux coordinate parsing, twin merge, burst clicking (126 passing). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
111 lines
3.9 KiB
JavaScript
111 lines
3.9 KiB
JavaScript
'use strict';
|
|
|
|
const { pointInBounds } = require('./click-frames');
|
|
|
|
/**
|
|
* Coordinate-space conversion between physical (OS event) pixels and
|
|
* Electron DIP points.
|
|
*
|
|
* Why this exists: OS-level click hooks report *physical* pixels (the X11
|
|
* root window space on Linux, virtual-screen pixels on Windows), while
|
|
* everything Electron-side — display bounds, cursor reads, the click-marker
|
|
* math in storeFrameAsStep — is in DIP. Mixing the two spaces is exactly the
|
|
* bug that makes the red marker drift on scaled displays: at 150% scaling a
|
|
* physical click at (1500, 900) is the DIP point (1000, 600), and a marker
|
|
* drawn at the physical values lands well below-right of the real click.
|
|
*
|
|
* On Windows, Electron exposes screen.screenToDipPoint() and the capture
|
|
* service prefers it. On Linux/X11 there is no such API, so we reconstruct
|
|
* the mapping from display geometry: each display's DIP bounds plus its
|
|
* scaleFactor give its physical rectangle, and a physical point inside that
|
|
* rectangle maps back linearly. With mixed-DPI multi-monitor X11 setups the
|
|
* origin reconstruction is an approximation (X11 itself has a single global
|
|
* coordinate space), but it is exact for the overwhelmingly common cases:
|
|
* single display at any scale, and multi-display with a uniform scale.
|
|
*/
|
|
|
|
/** Physical-pixel rectangle a display occupies, derived from DIP bounds. */
|
|
function physicalBoundsOf(display) {
|
|
const bounds = display && display.bounds;
|
|
if (!bounds) return null;
|
|
const scale = display.scaleFactor || 1;
|
|
return {
|
|
x: Math.round(bounds.x * scale),
|
|
y: Math.round(bounds.y * scale),
|
|
width: Math.round(bounds.width * scale),
|
|
height: Math.round(bounds.height * scale),
|
|
};
|
|
}
|
|
|
|
function centerDistanceSq(point, rect) {
|
|
const cx = rect.x + rect.width / 2;
|
|
const cy = rect.y + rect.height / 2;
|
|
return (point.x - cx) ** 2 + (point.y - cy) ** 2;
|
|
}
|
|
|
|
/**
|
|
* Display whose physical rectangle contains the point, or the nearest one
|
|
* (clicks on the very edge of a screen can round to one pixel outside it).
|
|
*/
|
|
function displayForPhysicalPoint(point, displays) {
|
|
if (!point || !Array.isArray(displays) || !displays.length) return null;
|
|
let nearest = null;
|
|
let nearestDist = Infinity;
|
|
for (const display of displays) {
|
|
const phys = physicalBoundsOf(display);
|
|
if (!phys) continue;
|
|
if (pointInBounds(point, phys)) return display;
|
|
const dist = centerDistanceSq(point, phys);
|
|
if (dist < nearestDist) {
|
|
nearestDist = dist;
|
|
nearest = display;
|
|
}
|
|
}
|
|
return nearest;
|
|
}
|
|
|
|
/**
|
|
* Convert a physical-pixel point (OS click hook) to DIP. Returns null when
|
|
* no display geometry is available — the caller should then fall back to a
|
|
* live cursor read rather than guessing.
|
|
*/
|
|
function physicalToDip(point, displays) {
|
|
if (!point || !Number.isFinite(point.x) || !Number.isFinite(point.y)) return null;
|
|
const display = displayForPhysicalPoint(point, displays);
|
|
if (!display) return null;
|
|
const phys = physicalBoundsOf(display);
|
|
const scale = display.scaleFactor || 1;
|
|
return {
|
|
x: display.bounds.x + (point.x - phys.x) / scale,
|
|
y: display.bounds.y + (point.y - phys.y) / scale,
|
|
};
|
|
}
|
|
|
|
/**
|
|
* Display whose DIP bounds contain the point, or the nearest one. Used to
|
|
* route a click to the capture stream of the monitor it landed on.
|
|
*/
|
|
function displayForDipPoint(point, displays) {
|
|
if (!point || !Array.isArray(displays) || !displays.length) return null;
|
|
let nearest = null;
|
|
let nearestDist = Infinity;
|
|
for (const display of displays) {
|
|
if (!display || !display.bounds) continue;
|
|
if (pointInBounds(point, display.bounds)) return display;
|
|
const dist = centerDistanceSq(point, display.bounds);
|
|
if (dist < nearestDist) {
|
|
nearestDist = dist;
|
|
nearest = display;
|
|
}
|
|
}
|
|
return nearest;
|
|
}
|
|
|
|
module.exports = {
|
|
physicalBoundsOf,
|
|
displayForPhysicalPoint,
|
|
displayForDipPoint,
|
|
physicalToDip,
|
|
pointInBounds,
|
|
};
|