Reported: "当有新固件时,在主面板顶部要显示有升级信息。点击跳转到设置的软件更新." The banner is cheap; the reason it did not exist is that nothing on the main panel could know about a release. `useUpdateFlow` was mounted only inside Settings > 软件更新, so closing that panel dropped the only copy of the state. Mounting a second copy is what the hook already supports — it reads the status Rust remembers and subscribes to the broadcasts Rust already sends, so neither view issues an extra network check, and the banner survives closing Settings. The notice is persisted, which is the part without an obvious answer. The probe runs at most once a day, so a remembered status that lives only in memory makes "available" visible on the morning it is discovered and invisible every launch after — including the launch straight after an update installs, exactly when the user is most likely to look. Measured, not theorised: the first launch showed no banner, and ageing the probe stamp was the only way to make one appear. Remembering a claim means being wrong about it later, so a restored notice is re-judged rather than trusted. A version that no longer leads is dropped, since the user is already running it; `ready` keeps its promise only while the installer file is really on disk, and otherwise says `available`, which is still true and merely means downloading again. Restore runs before `setup_tray` so the tray row cannot contradict the banner, and a copy told to stop checking restores nothing, because that switch means "don't tell me". Two banners that used to be mutually exclusive now stack. An update notice and a broken screen-recording permission are different news, and chaining them meant a user who fixed the first never learned the second existed. Co-Authored-By: Codex <noreply@openai.com> |
||
|---|---|---|
| .. | ||
| components | ||
| lib | ||
| App.tsx | ||
| i18n.ts | ||
| main.tsx | ||
| styles.css | ||
| types.ts | ||