http://bugs.winehq.org/show_bug.cgi?id=27711
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #6 from Nikolay Sivov bunglehead@gmail.com 2011-07-21 04:14:24 CDT --- (In reply to comment #5)
Tried this:
static BOOL LISTVIEW_SetTextBkColor(LISTVIEW_INFO *infoPtr, COLORREF color) { FIXME("(oldcolor=%x)\n", infoPtr->clrTextBk); FIXME("(newcolor=%x)\n", color);
When I check and then uncheck, I get:
fixme:listview:LISTVIEW_SetTextBkColor (oldcolor=ffffff) fixme:listview:LISTVIEW_SetTextBkColor (newcolor=ffffffff) fixme:listview:LISTVIEW_SetTextBkColor (oldcolor=ffffff) fixme:listview:LISTVIEW_SetTextBkColor (newcolor=ffffff)
3rd line, color was already white? Expecting to see oldcolor ffffffff. Possibly this is why there was invalidate loop?
There's no invalidation with native module in any case, so a fix is right I think. Initial problem is fixed, so yes, please open a new bug for transparency problem.