http://bugs.winehq.org/show_bug.cgi?id=15848
--- Comment #16 from malzfreund@hotmail.com 2009-06-16 18:23:52 --- (In reply to comment #15)
Status shoud be changed to RESOLVED or CLOSED or something like that imho.
This problem does not appear in PokerTracker 3 beta 27+ (and likely also won't appear in the soon-to-be-released stable version PokerTracker 3.00 build 5).
No workaround needed anymore. Tested with 1.1.19.
Sry didn't know how to edit #15. I guess I am trying to say that this bug is only an issue with versions of PokerTracker 3 that are now obsolete.