Files
ltk/tests/overlay_reconciliation.rs
Pedro M. de Echanove Pasquin ce893ac776
Some checks are pending
CI / build + test (push) Waiting to run
CI / cargo audit (push) Waiting to run
responsive fluid/physical scaling, widget-API stabilization, and perf guardrails
Responsive scaling. ltk now offers two first-class ways to size a UI so it adapts across screens, chosen per process via `WidgetScaling { Fluid, Physical }` (`set_widget_scaling` / `widget_scaling`, default `Fluid`). Fluid sizing (`Length::fluid( px )`) makes a design pixel a proportion of the surface's smaller side, calibrated against a reference width (`set_fluid_reference` / `fluid_reference`, 412 px default) and bounded by `FLUID_MIN` / `FLUID_MAX`; physical sizing (`Length::dp( px )`) is a constant-physical-size pixel scaled by display density (`set_density` / `density`). `Length` gains `orient( portrait, landscape )` — resolve one value in portrait, another in landscape — plus `widget( px )`, which picks fluid or dp per the active mode. Canvas exposes `geom_px` (geometry, resolved in physical layout space) and `font_px` (font size, bridging logical / physical per mode) so widgets and apps share one resolution path. Note the rename: `set_design_reference` / `design_reference` became `set_fluid_reference` / `fluid_reference`, and `Length::dp` changed meaning — the old surface-proportional behaviour now lives on `Length::fluid`.
Widgets. Every stock widget resolves its default geometry and font through the widget-scaling mode instead of frozen pixels, so a whole UI scales coherently without per-call units. New size builders where they were missing: `button` gains `font_size` / `height`, `text_edit` gains `height` / `font_size_fluid`, `separator` gains `pad_v`, and assorted widgets accept a `Length` where they previously took only `f32`.
Overlays. `OverlaySpec::size` is now `( Length, Length )` instead of `( u32, u32 )`, resolved against the main surface when the overlay is materialized, so overlays can scale with the display; `Length::px( … )` reproduces the old fixed sizing.
API stabilization (toward 1.0). Widget struct fields are now `pub( crate )` — they are configured through builders, not field access — except the value / state types apps genuinely read or construct (`Time`, `Date`, `ComboState`), which stay public. The internal `test_support` helpers move behind a `test-support` Cargo feature (off by default, so third-party builds never see them; ltk's own `make test` enables it). `Separator` drops its `0.0`-means-mode sentinel for `Option<Length>`, so an explicit `pad_v( 0.0 )` is a real flush divider distinct from the mode-following default.
Performance guardrails. Opt-in diagnostics via `LTK_PERF_WARN=1` warn about stuck animations, sustained software-render animation, and low `poll_interval`; software-rendered animation is capped near 30 Hz to spare CPU on machines that fall back off EGL. Apps can override the cap with `App::cap_software_animation`.
Docs and build. The two scaling modes are documented in README, onboarding and architecture, with the earlier gradient / backdrop doc drift cleaned up. The Makefile now ships the `locales/` directory into the packaged crate (fixing i18n keys rendering raw for downstreams), builds the new `responsive` example, and runs tests with `--features test-support`.
2026-07-07 17:40:33 +02:00

88 lines
2.3 KiB
Rust

#![ cfg( feature = "test-support" ) ]
use ltk::test_support::diff_overlay_ids;
use ltk::OverlayId;
fn ids( xs: &[ u32 ] ) -> Vec<OverlayId>
{
xs.iter().copied().map( OverlayId ).collect()
}
#[ test ]
fn empty_to_empty_is_no_change()
{
let ( added, removed ) = diff_overlay_ids( ids( &[] ), &ids( &[] ) );
assert!( added.is_empty() );
assert!( removed.is_empty() );
}
#[ test ]
fn first_frame_marks_everything_added()
{
let ( added, removed ) = diff_overlay_ids( ids( &[] ), &ids( &[ 1, 2, 3 ] ) );
assert_eq!( added, ids( &[ 1, 2, 3 ] ) );
assert!( removed.is_empty() );
}
#[ test ]
fn empty_next_marks_everything_removed()
{
let ( added, removed ) = diff_overlay_ids( ids( &[ 1, 2, 3 ] ), &ids( &[] ) );
assert!( added.is_empty() );
let mut removed_sorted = removed;
removed_sorted.sort();
assert_eq!( removed_sorted, ids( &[ 1, 2, 3 ] ) );
}
#[ test ]
fn unchanged_set_produces_no_diff()
{
let ( added, removed ) = diff_overlay_ids( ids( &[ 1, 2, 3 ] ), &ids( &[ 1, 2, 3 ] ) );
assert!( added.is_empty(), "no overlays should be added" );
assert!( removed.is_empty(), "no overlays should be removed" );
}
#[ test ]
fn order_in_next_does_not_matter_for_diff()
{
// Same set, different order — the overlay surfaces should be reused, not
// recreated.
let ( added, removed ) = diff_overlay_ids( ids( &[ 1, 2, 3 ] ), &ids( &[ 3, 2, 1 ] ) );
assert!( added.is_empty() );
assert!( removed.is_empty() );
}
#[ test ]
fn open_one_panel_marks_only_it_added()
{
let ( added, removed ) = diff_overlay_ids( ids( &[ 1 ] ), &ids( &[ 1, 2 ] ) );
assert_eq!( added, ids( &[ 2 ] ) );
assert!( removed.is_empty() );
}
#[ test ]
fn close_one_panel_marks_only_it_removed()
{
let ( added, removed ) = diff_overlay_ids( ids( &[ 1, 2 ] ), &ids( &[ 1 ] ) );
assert!( added.is_empty() );
assert_eq!( removed, ids( &[ 2 ] ) );
}
#[ test ]
fn swap_one_panel_marks_one_added_one_removed()
{
let ( added, removed ) = diff_overlay_ids( ids( &[ 1, 2 ] ), &ids( &[ 1, 3 ] ) );
assert_eq!( added, ids( &[ 3 ] ) );
assert_eq!( removed, ids( &[ 2 ] ) );
}
#[ test ]
fn added_preserves_next_order()
{
// Creation order is deterministic — the runtime instantiates new
// surfaces in the order the app returned them, and diffing must
// preserve it.
let ( added, _removed ) = diff_overlay_ids( ids( &[] ), &ids( &[ 7, 3, 5 ] ) );
assert_eq!( added, ids( &[ 7, 3, 5 ] ) );
}