Jeremy Leibs

Note: can't repro on 0.12.0 so suspect this is related to the the egui / wgpu update rather than another regression in chrome itself.

Bisection: - Last commit where I cannot reproduce: https://app.rerun.io/commit/5bfb48e/index.html - From bd64926 -> a1a4df2 Unknown state since rerun will not load on Chrome (Failed to create wgpu adapter, no suitable...

Also worth noting, forcing `renderer=webgl` doesn't resolve the issue. So it's not related to the try-then-fallback logic.

Another observation: (1) This is very reminiscent of https://github.com/rerun-io/rerun/issues/3931 (2) During the range where we weren't able to test on chrome we added https://github.com/rerun-io/rerun/pull/4877 which added just a bit more...

Confirmed: reverting https://github.com/rerun-io/rerun/pull/4877 remedies the problem.

This has been done.

Related to the last random thought: Generic ScalarBatch is pretty common way of thinking about and representing large state-space control-systems. However, in that case the user would still want to...

If we make app an explicit, selectable concept rather than an implicit grouping of recordings I think it warrants its own close button somewhere.

Proposal for 0.15 as simplest thing that works: - Two blueprints per app-id: one "active", one "stored" - Incoming blueprint always updates "stored" and only makes the stored blueprint active...

Optional improvement: - Advanced UI menu on recording selection to activate a **specific** blueprint instead of only ever allowing user to activate he last one.