Skip to content

Releases: philippremy/WavyBackgrounds

WavyBackgrounds - v0.1.2

13 Dec 13:29

Choose a tag to compare

WavyBackgrounds v0.1.2

This is a universal binary for macOS (x86_64 and aarch64/arm64).

Changelog

  • Fixed an issue where the Rust backend panics because the Aerial.sqlite database has a different structure (columns are fetched by name from now on)

WavyBackgrounds - v0.1.1

06 Dec 11:06

Choose a tag to compare

WavyBackgrounds v0.1.1

This is a universal binary for macOS (x86_64 and aarch64/arm64).

Changelog

  • Removed cURL as a dependency (incompatibilities when used in an async environment)
  • Reworked ObjC window handling by using unique window identifiers
  • Fix double free problems, where ObjC ARC and the NSWindow class would try to free the same object twice
  • Implemented function to remove dynamic backgrounds on the current (active) space
  • When applying a video, which was not cached before, it will be downloaded first (instead of silently crashing the application)

WavyBackgrounds - v0.1.0

02 Dec 19:36

Choose a tag to compare

DO NOT USE!

Problem occurs during execution (double free, malloc). Interestingly enough only in Release Builds, Debug Builds (i.e., with hot reload) work just fine.

WavyBackgrounds v0.1.0

This is a universal binary (x86_64 and aarch64/arm64).

Changelog

  • Switched to the Tauri frontend and uses Rust as the backend language now
  • Is independent of any video files, which one had already downloaded via the System Settings
  • Now has a System Tray
  • Backgrounds don't move around in spaces
  • Backgrounds stay in place when Mission Control is used

Missing implementations

  • Ability to close the dynamic background on the active space only1
  1. Skeleton code is commented out, always got a SEGFAULT (ERR_BAD_ACCESS) during testing. Could very well be because of the somewhat unstable state of the objc crate.

v0.1 Alpha

31 Oct 18:05

Choose a tag to compare

v0.1 Alpha Pre-release
Pre-release

Can do basic stuff. Look for the Sonoma videos, show a little example picture and finally launch the newly created NSWindow with the video player. Currently is relatively energy intensive.