YourWishes
b639bc6c4f
The old widget system (archive/dusk/ui/) depended on infrastructure this rewrite deleted -- a static X-macro element list, a 9-slice UI_FRAME, and a global gamepad/keyboard focus stack -- so everything below is rebuilt on top of the new native uielement_t pool + parent/child tree instead, gamepad/keyboard-only (no mouse support exists in the input system). New JS widgets (assets/scripts/), all pure composites of Label/Rectangle following the Button.js pattern: Checkbox, Tab, Slider, Dropdown. Slider/ Dropdown expose a directionInput(dx, dy) hook so a menu can hand them LEFT/RIGHT before falling back to cursor movement. New Menu.js replaces the old global uifocus_t stack: a small push/pop stack of Menu instances where only the topmost consumes CANCEL/ACCEPT/ direction input each tick (needed for nested modals -- a Settings sub-page menu plus a "discard changes?" Confirm can be open at once). Held-direction repeat timing matches the old 0.5s delay / 0.1s repeat. New overlay composites (added via a new UI.addOverlay()/UI.removeOverlay(), always drawn/updated after normal roots): FpsCounter, ConsoleOverlay (one Label per console history line, driven directly rather than via add() since History (16) exceeds the 8-children-per-element cap), Crop (letterbox/pillarbox bars), and Fullbox (a reusable tweened full-screen fade covering both the old fullbox and transition effects -- reuses shared instances rather than allocate-and-dispose, since disposing an element from inside its own render() callback risks the same JerryScript refcount corruption hit earlier in this rewrite). New Confirm.js (Yes/No dialog) and Settings.js (+ SettingsGeneral/ SettingsInput sub-pages) built on Menu. Display/Audio settings pages are intentionally not ported -- neither had a real backing engine system even in the old code. Frame is a flat Rectangle for now, not real 9-slice (a genuinely bigger native lift, deliberately deferred). Small native binding additions needed by the above, each with its own unit test: Time.renderDelta, Console.lineCount/getLine/visible/ consumeDirty, a new Screen module, a new Locale module, Input.deadzone, a new Save module, and Label.color (was missing entirely). Also fixes a real gap from the UI.addOverlay() work: uiElementDispose() wasn't removing disposed elements from the new overlay root array, which would have left dangling ids behind. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
44 lines
1.4 KiB
JavaScript
44 lines
1.4 KiB
JavaScript
// Copyright (c) 2026 Dominic Masters
|
|
//
|
|
// This software is released under the MIT License.
|
|
// https://opensource.org/licenses/MIT
|
|
|
|
// extends UIElement (not Label) deliberately: only a UIElement/SCRIPTED
|
|
// instance's render()/update() override actually gets dispatched by the
|
|
// engine (the native Label/Rectangle callback tables never consult a
|
|
// subclass's override -- they're not scripted types themselves). So this
|
|
// composes a child Label instead of subclassing one, same as Button.
|
|
//
|
|
// Overrides render() rather than update(): update()/uiUpdate() only run
|
|
// on the one fixed-timestep tick per real frame that actually crosses a
|
|
// DUSK_TIME_STEP boundary (see Time.renderDelta's doc), but an FPS
|
|
// counter needs to sample every real frame -- which is exactly what
|
|
// render() does.
|
|
class FpsCounter extends UIElement {
|
|
init() {
|
|
this.label = new Label();
|
|
this.add(this.label);
|
|
|
|
this._average = 0;
|
|
}
|
|
|
|
render() {
|
|
const delta = Time.renderDelta;
|
|
if(delta > 0) {
|
|
const fps = 1 / delta;
|
|
this._average = this._average === 0
|
|
? fps
|
|
: this._average + (fps - this._average) * FpsCounter.SMOOTHING;
|
|
}
|
|
|
|
this.label.text = 'FPS: ' + Math.round(this._average);
|
|
this.renderChildren();
|
|
}
|
|
}
|
|
|
|
// Exponential-moving-average weight per sample -- lower is smoother/
|
|
// slower to react, higher tracks instantaneous frame time more closely.
|
|
FpsCounter.SMOOTHING = 0.1;
|
|
|
|
module.exports = FpsCounter;
|