---
title: "Comment by Adam Lewis on \"How Live Wallpapers Render Beneath Your Desktop Icons on Windows\" | Hashnode"
description: "Windowing is where I expect this gets nasty. Compositing beneath the icon layer means working against a surface that was never designed to have anything behind"
url: "https://hashnode.com/posts/how-live-wallpapers-render-beneath-your-desktop-icons-on-windows/6ac258dab4f5af9afc5581f3/comment/6acbf7e5f207f3ca0e735610"
---

[Discussion](https://hashnode.com/posts/how-live-wallpapers-render-beneath-your-desktop-icons-on-windows/6ac258dab4f5af9afc5581f3)

Comment [How Live Wallpapers Render Beneath Your Desktop Icons on Windows](https://hashnode.com/posts/how-live-wallpapers-render-beneath-your-desktop-icons-on-windows/6ac258dab4f5af9afc5581f3)

[Adam Lewis](https://hashnode.com/@nark3d)

[Oct 11](https://hashnode.com/posts/how-live-wallpapers-render-beneath-your-desktop-icons-on-windows/6ac258dab4f5af9afc5581f3/comment/6acbf7e5f207f3ca0e735610)

Windowing is where I expect this gets nasty. Compositing beneath the icon layer means working against a surface that was never designed to have anything behind it, so tell me how you handled it. Does the engine own a child window of the desktop, or does it hook the composition pass itself? Does the same approach survive a multi-monitor setup where each display has its own wallpaper and its own refresh rate?