hrynco/hrynco-kswitcher
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 41 Wiki Activity

Release v0.6.3: fix capture banner ordering and check updates periodically

Browse Source
This commit is contained in:
Anatolii Hrynchuk
2026-10-29 13:06:58 +02:00
parent 6b180798f5
commit d28e28c03c
16 changed files with 69 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Release/README.md
+10 -10
View File
@@ -1,17 +1,17 @@
# Latest Windows release
## v0.6.2 — 2026-10-29
## v0.6.3 — 2026-10-29
- Add **Open editor after screen capture**, enabled by default. Disable it to use notification-first capture; an immediate notification error still opens the editor.
- Save the preference and apply it to each capture, including requests sent to an already running screenshot process.
- Register screenshot notification identity, shortcut and COM activation during resident startup, as well as before sending a notification.
- Log notification registration and submission errors when logging is enabled.
- Refresh clipboard history preview row heights when display DPI changes.
- Hide the fullscreen capture selection before submitting a notification when automatic editor opening is disabled. Previously the selection remained visible during submission, which could suppress the banner under Windows fullscreen notification rules.
- Default to capture → notification → click → editor. **Open editor after screen capture** is now off by default; explicitly saved preferences are preserved.
- Retain the editor fallback for immediate notification errors.
- Check for updates in the background every 6 hours after the startup check. Notify once per version per session, retry after network failures at the next interval, and install only after confirmation.
Verified: 175 native checks, 397 input/layout checks at 240 DPI, screenshot editor UI integration,
isolated notification registration checks, and 45 updater checks. A physical transition between
monitors with different DPI has not been tested. Successful notification submission does not
guarantee a visible Windows banner; asynchronous toast failures are not yet monitored.
Verified: 176 native checks, 403 input/layout checks at 240 DPI, screenshot editor UI integration,
isolated notification registration checks, and 45 updater checks. The new UI regression test failed
before the fix and passes afterward: the selection is hidden at notification submission.
Banner behavior still needs confirmation on the affected laptop. Windows Do Not Disturb can
send notifications directly to the notification center; asynchronous toast failures are not yet monitored.
**Upgrade:** choose Update in the tray menu. Legacy v0.3.0–v0.4.1 clients first receive the
v0.4.2 compatibility bridge, then the current full release. v0.2.3 and earlier require manual installation.