http://bugs.winehq.org/show_bug.cgi?id=15118
--- Comment #14 from Will Tipton wtipton@hmc.edu 2009-07-06 16:18:33 --- It seems there was some progress working on this problem as of 1.1.24: it seems to be closer to behaving correctly. So, I think a status update is in order. I'll attach and describe an image of the app as it runs currently and hypothesize about what might be unusual about the app that wine gets wrong. Hopefully someone with more knowledge of wine/windows internals will be able to flesh out the specifics.
So, the HUD is a single window called PokerTracker3TableCover which pops up and overlays the poker site's software. Although PT3 itself provides transparency options, the transparency shown in the screenshot was achieved with Compiz. Now, the idea of the HUD is that the regions of the window which are red in the screenshot display information about the players at the table. The rest of the window, which is black in the screenshot, should not be visible at all. And, of course, when the user clicks on the black portion of the window, the mouse press should be passed on to the poker software behind it. In other words, the black portion of the window should not be there.
So that is the problem with PT3's current behavior in wine: the non-information-containing of the HUD window should be transparent and should not recieve mouse clicks. Now, I imagine that this is implemented in PT3 through some Layered Windows attributes which are not supported by wine. According to http://www.codeproject.com/KB/wtl/transparent.aspx , WS_EX_LAYERED makes the window see-through and WS_EX_TRANSPARENT makes it click-through. So, if we could verify that these are not working in wine and then take steps to implement them, maybe we could close this bug. :)