v1.6.0

Features

• enable runtime cli commands by @lukeyou05 in #85

Bug Fixes

• scale border effects based on dpi
• update window rect and position after rescaling or resizing
• persist komorebi color changes during brush recreation

Full Changelog: v1.5.0...v1.6.0

v1.5.0

Features

• add theme-aware border colors for Windows by @Louis047 in #74

Bug Fixes

• fix borders disappearing after waking system from sleep

Full Changelog: v1.4.1...v1.5.0

v1.4.1

Bug Fixes

• properly update version shown in tooltip

Full Changelog: v1.4.0...v1.4.1

v1.4.0

Features

• add auto-start on system boot by @iKineticate in #50
• add optional spread parameter for effects by @Louis047 in #67

Bug Fixes

• draw border as square when radius is set to 0
• poll window state because some events can be unreliable
• ensure borders are destroyed ASAP
• improve z-order handling for BelowWindow mode and prevent ghost borders by @Louis047 in #66
• debounce consecutive reorders by @lukeyou05 in #68

Full Changelog: v1.3.1...v1.4.0

Nevermind, we're not changing the default z-order this release.

v1.3.1

Bug fixes

• prompt user when starting multiple instances to prevent unwanted instances
• retry komorebi subscription until successful
• ensure resources are cleaned up by switching to RAII patterns by @lukeyou05 in #46
• destroy borders before application exit to ensure proper cleanup
• create logger earlier to ensure all logged messages are handled
• re-render border when system resumes from sleep/hibernation
• adjust radius for snapped windows when using Auto radius mode
• replace is_rect_visible with is_window_minimized to improve multi-monitor support
• preserve error source chains by @lukeyou05 in #43

Full Changelog: v1.3.0...v1.3.1

In the next release, border_z_order's default value will change from AboveWindow to BelowWindow to improve stability. If you want to keep the current behavior, you should explicitly define border_z_order in the config.yaml if you haven't already.

v.1.3.0

Features

• add config option to ignore Windows' native border visibility
• add config option to disable logging
• add config option to place border below its corresponding window to fix flickering with certain applications
• allow custom config directories via the "TACKY_BORDERS_CONFIG_HOME" environment variable

Bug fixes

• improve stability of V2 render backend (#42) (may still have issues on Windows 10, please report any)
• adjust logger's time to match local clock
• clamp opacities from the negative side during fade animation to prevent visual glitches
• disable borders for tacky-borders' own windows to prevent some lingering borders
• apply komorebi colors immediately upon border creation
• periodically prune komorebi integration resources to prevent memory leaks
• update komorebi integration for komorebi v0.1.37
• ensure the internal active window is updated when restoring a window from the taskbar on Windows 10

Full Changelog: v.1.2.0...v1.3.0

v.1.2.0

Features

• add option to match based on process name for window rules
• add V2 rendering backend option to support new effects (#22)
• add drop shadow and outer glow effects (#22)

Bug fixes

• ensure fade animation works with a single active/inactive list entry
• bypass tracking windows' dpi awareness when scaling border for hidpi displays
• account for windows version when determining border radius
• adjust border offset based on monitor dpi
• improve reliability of "reload borders"
• expand window rect for positive border offsets
• stop komorebi integration if komorebic subscribe-socket command fails

Full Changelog: v1.1.0...v.1.2.0

NOTE: There are some known issues with the new V2 render backend, especially when running Windows 10. If you're using such a setup, you may want to hold off on updating for now until the issues are resolved. Alternatively, you can switch back to the Legacy render backend within the config.

v1.1.0

Features

• implemented komorebi integration to allow different colors for stack, monocle, and floating windows (#20)
• added pop-up window that displays when an invalid config option is encountered

Bug fixes

• added retries for config reloads to workaround config watcher race conditions
• ensured custom border radius always appears the same, regardless of border width

Full Changelog: v1.0.0...v1.1.0

v1.0.0

Features

• Gradients for the active and inactive colors
• Three animation effects, along with customizable duration and easing types
• A log at ~/.config/tacky-borders
• Tooltip for the tray icon to show current version
• Ability to force enable borders from the config
• HiDPI support
• Config watcher to automatically reload borders when the config changes

Bug fixes

• Use the unminimize delay when restoring/unminimizing windows after switching workspaces
• Prevent the border from being incorrectly hidden/destroyed for apps like emacs
• Prevent the border from flashing when typing for apps like firefox
• Update the border color for some apps more reliably
• Recreate direct2d resources after waking up from sleep
• Log invalid config errors in the log file instead of crashing, and just prevent crashes in general
• Use the unminimize delay when restoring windows that were minimized when tacky-borders was launched

Many thanks to @0xJWLabs @kleineluka @amnweb

v0.3.0

• Added window_rules to allow customization on a per-app basis
• Added init_delay and unminimize_delay config options
• Updated the default config.yaml with examples
• Adjusted default border radius
• Many bug fixes

NOTE:
This release is incompatible with the config formats of previous releases, so you MUST delete your config.yaml if you have one. It is located in %userprofile%/.config/tacky-borders.