PlasmaZones 3.2.2

7 changes, released July 18, 2026.

Added

  • Fuller support reports: the support report archive now includes your rules, quick layouts, layout settings and settings profiles, with home paths redacted, and the daemon’s report gains a Rules section. Earlier reports were missing these files, which made several bug reports slow to diagnose. (#795, #796, #797)

Fixed

  • Global animation settings work again: since 3.2.0, window animations ignored the global Duration and Curve settings and always played at a fixed 200 ms. Windows follow the global settings again, and a per-event override still wins where you set one. (#795, #797)
  • Cross-monitor moves no longer hop sideways: moving a window down or up to another monitor could jump to a monitor beside the current one when your monitors have different heights. The move now only targets a monitor that actually lines up in the direction of the move. (#795, #797)
  • Settings survive concurrent writers: when the settings app and the daemon wrote the configuration at the same time, a stale in-memory copy could resurrect old values over a just-saved change, and an external change notification could silently drop unsaved edits. Both paths now stay coherent. (#797)
  • Per-page Reset and Discard stay on their page: on the Decoration and Animations settings families, resetting or discarding one page could also revert its sibling pages. Each page now only touches its own settings. (#794)
  • Resetting OSD and Popup decorations restores the built-in look: resetting the Appearance → Decorations → Surfaces → OSDs or Popups page removed the built-in card border and shadow instead of restoring them. The built-in chrome is now a default layer underneath your edits, so reset brings it back, and setups that had already lost it get it back without doing anything. (#798)
  • Upside-down decorations on OpenGL: window decorations could render flipped vertically on the OpenGL backend when two or more decoration packs were combined, and during show or hide transitions. The Vulkan backend was unaffected. (#798)