WinKit 1.1.0

WinKit 1.1.0

Adds error reporting and auto-updates, plus reliability fixes found through real use.

Fixed

• Custom theme saving could crash the app. Saving a theme while another save was in flight (e.g. toggling a setting right after hitting Save) could throw a FileNotFoundException and show an error dialog. The root cause was a race condition in how settings/theme files were written to disk. Persistence now serializes writes per file, uses an atomic file swap instead of copy-then-delete, and automatically recovers if a file is ever found corrupted (it's quarantined for inspection instead of crashing the app on every future launch).
• Saving a custom theme could visually flash back to a built-in theme for an instant right as the save completed, before settling back on your custom theme. This was a UI state bug in how the theme list refreshed, not a persistence issue — nothing was actually lost, but it looked alarming.
• A light or pastel custom accent color could make button text unreadable. The color used for text drawn on top of the accent color ("Text on accent") wasn't actually part of the theme system — it was hardcoded. It's now a real, customizable field in the theme editor.
• Custom themes could get the wrong titlebar color mode. Whether the window chrome renders in dark or light mode was being decided by the theme's name instead of its actual background color, so a custom theme could end up with mismatched titlebar styling.
• Mica and Acrylic window materials didn't actually do anything visually, regardless of which one you picked in the theme editor — an opaque layer was unintentionally covering the translucent window surface. Both materials now render correctly.
• "Off" animation intensity didn't disable animations. The notification fade-in/fade-out now genuinely turns off when animation intensity is set to Off, instead of always animating regardless of the setting.

Added

• Error reporting ("Send to Developers"). When WinKit hits an unexpected error, you'll now see a dialog with Preview, Close, and Send to Developers. Preview shows the exact report that would be sent — WinKit version, Windows version, architecture, the failing component, exception details, and a timestamp — before you decide whether to send it. Nothing is ever sent automatically or silently; it only goes out if you click Send. Reports never include user files, credentials, activity history, full settings, or theme contents. If sending fails (e.g. no connection), the report isn't lost — you can retry or copy it manually.
• Automatic updates. WinKit now checks GitHub Releases for a newer version on startup and periodically in the background (checks never block startup or the UI). You can also trigger a manual check from Settings → About. When an update is available you can install it, skip that specific version, or dismiss it and get reminded later — and automatic checking can be turned off entirely if you'd rather not be notified. Downloads are SHA-256 checksum-verified before anything runs, and the actual file replacement always happens via a separate small process after WinKit closes — never from inside the running app itself. Your settings, custom themes, and activity history are untouched by an update either way.

Downloads

• WinKitSetup-1.1.0.exe (recommended) — installs to Program Files, adds a Start Menu shortcut, registers a normal uninstaller.
• WinKit-1.1.0-win-x64-portable.zip — no installation; extract anywhere and run WinKit.exe.

Both are self-contained (the .NET runtime is bundled — nothing else to install) and require Windows 10 (build 22000+) or Windows 11, 64-bit. No account, no telemetry, nothing runs in the background beyond WinKit itself.

Full Changelog: 1.0.0...1.1.0