That’s not it. This is the commit that puts the timer and the call to isWindowOnCurrentVirtualDesktop, fixing this bug. It was followed by this and this, fixing this subsequent bug. Basically, in a quite corner case you could get your drop shadows floating alone in the wrong desktop. The issue seems to be that Windows doesn’t notify when the user has moved to another virtual desktop, so you have to ask it regularly, hence the timer callback doing just that. It’s a 5 Hz timer, so it shouldn’t impact performance noticeably, but I recall from working on the subsequent bug that the system call itself is quite costly in Debug, getting heavily optimized in Release.
1 Like