http://bugs.winehq.org/show_bug.cgi?id=29251
--- Comment #5 from Austin English austinenglish@gmail.com 2011-12-07 12:33:40 CST --- (In reply to comment #2)
Could you reopen this with Importance set to Enhancement then? There have been many other cases where "noisy" fixmes have been dealt with, so I think this is a valid enhancement request.
No, fixme's are not bugs in and of themselves, please don't file more.
Some examples of previous similar commits; I've marked ones you committed yourself with (*): cmd: Quiet a noisy 'FOR /F' fixme. d3dx9_36: Quiet a noisy fixme. tapi32: Quiet a few noisy fixme's. xinput1_3: Quiet a noisy fixme. uxtheme: Quiet a noisy fixme. imm32: Quiet ImmGetOpenStatus fixme. (*) dwmapi: Silence a noisy fixme. mscms: Quiet a noisy fixme. ddraw: Display fixme only once in IDirectDrawImpl_WaitForVerticalBlank. ddraw: Display fixme only once in IDirect3DVertexBufferImpl_Optimize. gdi32: Quiet a noisy fixme. (*) wininet: Quiet a noisy fixme. (*) advapi32: Quiet a noisy fixme. (*)
Yes, I'm aware, though it's not worth opening a bug over, just send a 1 minute patch.
Another noisy d3d-related fixme is this one: fixme:d3d_surface:wined3d_surface_blt Blit clipping not implemented.
There was opposition to silencing it on irc, so I won't send a patch for this (or bug 29264).