I’ve noticed that when running a Unity app in windowed mode in Windows XP, if you drag the window partway off of and then back onto the screen, you get a ‘smearing’ visual artifact that persists until the mouse button is released. Applications that use the Windows API directly don’t typically seem to have this problem, but it does seem to be common among cross-platform solutions such as Unity.
Just out of curiosity, is there any way to prevent this behavior in Unity? Or is it unavoidable?
I believe that the Windows version is pretty much a native DirectX implementation and does not use any cross platform tools as far as windowing is concerned.
while user is moving the window, do not render the game, or
while the user is moving the window, keep on rendering the game
We chose the first and so far no one objected about that. We can implement the second approach if that’s what people generally want. I personally don’t care if the game is not rendering the view while I’m moving the window.