https://bugs.winehq.org/show_bug.cgi?id=12060
--- Comment #32 from Stefan Dösinger stefan@codeweavers.com --- (In reply to Artem S. Tashkinov from comment #29)
Yes, they are linked. BTW displacement is seemingly random from invocation to invocation. I've now launched it again and the displacement is so huge I can only see 10% of the visualization.
But once started up, the displacement stays constant regardless of where the window is placed?
Does the problem also happen when you run winamp inside a virtual desktop?
What do you mean?
Winecfg->graphics->emulate a virtual desktop
Or wine explorer.exe /desktop=foo winamp.exe
What I want to get to with both questions: At least in ddraw (although reading from the bug history I guess milkdrop uses d3d9), primary surface coordinates are screen-relative, not window-relate. So when the app has a window placed at 123x3456 and wants to draw pixel 20x30 inside it, it actually draws pixel (123+20 x 456+30), and wine sort of undoes this because in GL everything is window-relative. We might get something wrong there in the way the application has set up its drawing. Because window placement involves the window manager, running inside a virtual desktop takes it out of the equation and lets wine do things on its own.