srdusr
aboutsummaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authorsrdusr <[email protected]>2025-12-03 22:52:00 +0200
committersrdusr <[email protected]>2025-12-03 22:52:00 +0200
commit393f886eb9e275c3b7a9e3ef396092ba71297dfb (patch)
treee84786279ff2216b1fa54c9fdad6ad57d8f73118 /tools
parent96aff79ae2df2ade1a29a68c1a8108d258596bc3 (diff)
downloadsrdwm-393f886eb9e275c3b7a9e3ef396092ba71297dfb.tar.gz
srdwm-393f886eb9e275c3b7a9e3ef396092ba71297dfb.zip
Stop giving tiled windows a shadow that lands on their neighbour
Diagnosed by a peer session (dotfiles-1a): SHADOW_SIZE is 24px, and a tiling layout with a small gap_inner (as little as 1px live) leaves the shadow nowhere to fall except onto the adjacent tile, darkening it by up to SHADOW_MAX_ALPHA (~35%) on whichever side is unfocused. Not a content tint or an opacity rule - verified against the actual rasteriser and the live rule set before accepting the diagnosis. A drop shadow separates a window from what's behind it; tiled windows are coplanar and adjacent by construction, with nothing behind them to separate from. redraw_decoration_buffer's shadow gate now requires w.floating in addition to the existing !maximized/!fullscreen checks. DecorationSignature gained a floating field so toggling floating on its own invalidates the decoration cache instead of waiting for an unrelated field to force a rebuild. Live-verified in a nested compositor: two tiled windows show a clean shared edge with no gradient bleeding across; floating a window still detaches it from the tile group with its shadow intact; shadows still toggle globally both ways.
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions