Previously, `Harness::run` just called `Harness::step` 3 times. If that wasn't enough, tests would often call run multiple times so all animations would finish properly. Also, I introduced `HarnessBuilder::with_step_dt` to customize with how big of a dt each frame is called. I set the default to 1.0 / 6.0 (~6fps) so we don't waste cpu in tests waiting on animations. `HarnessBuilder::max_steps` allows us to control how many steps `Harness::run` should run before panicing. The default is 6, so we run for up to 1.0 logical seconds (six frames at 6 fps), which should be enough to finish most animations. Turns out a lot of snapshots where rendered before fully shown and had a light opacity, those are now fixed. * [x] I have followed the instructions in the PR template |
||
|---|---|---|
| .. | ||
| src | ||
| tests | ||
| Cargo.toml | ||
| README.md | ||
README.md
egui demo app
This app demonstrates egui and eframe.
View the demo app online at https://egui.rs.
Run it locally with cargo run --release -p egui_demo_app.
egui_demo_app can be compiled to WASM and viewed in a browser locally with:
./scripts/start_server.sh &
./scripts/build_demo_web.sh --open
egui_demo_app uses egui_demo_lib.
Running with wgpu backend
(cd egui_demo_app && cargo r --features wgpu)