Skip to content

Create effects handler after letting toplevels setup compositing

Many effects use the stacking order property of the effects handler in their constructors. This means that windows should have compositing setup by the time effects are loaded.

After changing how binary effect plugins are loaded, i.e. not queueing loading effects, but loading them immediately, some effects broke because the effects handler is created before windows setup compositing.

This change attempts to fix those effects by rearranging compositor startup code so windows setup compositing first, then create the effects pointer.


How to test this merge request: enable blur effect, run qdbus org.kde.KWin /KWin reconfigure, and pay attention to the panel before and after running that command

Merge request reports