http://bugs.winehq.org/show_bug.cgi?id=28512
--- Comment #5 from AJSB ajsb@vfemail.net 2011-09-29 16:51:21 CDT --- Well i found a "workaround" for the bug using a AutohotKey script made by me !
I discovered that the mouse buttons , when playing and using their default bindings ( like i guess 99,99% of gamers do use them) were actually working well, only when they were used for other bindings they aren't at all (i made the experience of editing by hand the configuration files of the games because like i said when reporting about bug, it was impossible to it in the games binding menus).
That and the way they were behaving, led me to think that WINE is "scanning"/however_it_deals_with those buttons in an unusual way compared with Windows.
Based on that and taking in account that i have some experience with AutoHotKey in Windows, i installed ATK in the default wineprefix (i didn't used winetricks for that or for Steam BTW, because i believe that all apps should work under same prefix like with real Windows) and made a script that scans the mouse buttons and that "feedsback" the mouse buttons in a way fully recognizable by any Windows program/game...same technique can be used to solve problem with keyboard (i'm not using it because i always play with mouse+gamepad and never with mouse+keyboard and keuboard was working for normal tasks in games like writing the new name of the player,etc...instead the script "reads" gamepad events and "feedsback" keyboard keys).
now i can even use the games binding menus to make the rebindings ! :)
Not exactlly the most elegant solution...but till the WINE bug/problem is really fixed, it's a "solution".
A bit OT, but, the performance, with same game settings, is BETTER under WINE than in Windows XP :))