Release notes

BUGFIX

Panels no longer get permanently stuck on the error screen if they fail to load

If you switch panels and encounter a loading failure, you will no longer get permanently stuck on the error screen. While version 0.22.7 made switching panels faster, it had a flaw: if a panel failed to load and showed an error screen, it would "cache" that error screen, meaning you'd be stuck looking at that error every time you switched back until you restarted the app. The system has learned its lesson and now only caches successfully loaded panels; if it fails, it will simply try to reload it fresh next time. It's like a TV that records the last channel you watched — it used to record the blue screen of death and replay it for you endlessly, but now it only records actual broadcasts and knows to re-tune the antenna if it hits static.

Original changelog

Original changelogPanels no longer get permanently stuck on the error screen if they fail to load
**A panel that fails to load is no longer pinned to its error screen until restart**: the panel caching added in 0.22.7 stored whatever `build_view` returned — including the `ErrorPanelView` fallback shown when a panel's HTML can't be read — so once a load failed, switching back kept showing the error even after the file was available again. usage now caches only successfully-built web views; a failed build is shown but left uncached and rebuilt on the next switch, so a transient read failure recovers on its own.