Jose Luis Montañes 93b8981418 Fix waveform: timeStep increments by 1 per tick, waveZoom = px/step ...

Each simulation tick now advances timeStep by 1 instead of by simSpeed ms.
waveZoom directly controls pixels per step, so changing clock speed
(the real-time interval) doesn't affect visual wave width, but zooming does.
This matches GTKWave behavior where the x-axis represents clock cycles.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-03-19 22:18:45 +01:00

..

app.js

refactor: modularize into ES6 modules

2026-03-19 22:00:02 +01:00

constants.js

refactor: modularize into ES6 modules

2026-03-19 22:00:02 +01:00

events.js

fix: waveform zoom buttons - use 1.5x multiplier, show zoom level, remove wheel zoom

2026-03-19 22:10:44 +01:00

gates.js

feat: CLK toggles on Step, add pan/zoom (arrows, +/-, wheel, 0=reset)

2026-03-19 22:06:03 +01:00

renderer.js

feat: CLK toggles on Step, add pan/zoom (arrows, +/-, wheel, 0=reset)

2026-03-19 22:06:03 +01:00

simulation.js

fix: remove alert(), fix waveform zoom, add waveform scroll (wheel + ctrl+wheel)

2026-03-19 22:08:26 +01:00

state.js

feat: CLK toggles on Step, add pan/zoom (arrows, +/-, wheel, 0=reset)

2026-03-19 22:06:03 +01:00

waveform.js

Fix waveform: timeStep increments by 1 per tick, waveZoom = px/step

2026-03-19 22:18:45 +01:00