2007/11/26, Stefan Dösinger stefandoesinger@gmx.at:
Am Montag, 26. November 2007 12:17:07 schrieb Rafał Miłecki:
2007/11/7, Rafał Miłecki zajec5polish@gmail.com:
Bug is quite well decribed in: http://bugs.winehq.org/show_bug.cgi?id=5623 but if you don't understand this, I can try to explain more detailed.
So my request is someone try to fix this bug. Anyone have a free moment for this, please?
Really, not a chance for fixing this? I know you are busy, have own life, efc. but... maybe? Anyone, please?
The usual way for that is either to offer payment to someone to fix it, or fix it yourself.
Offering bug bounties was tried in the past, but I don't know how well they worked. The issue is that usually affordable bounties are not comparable to usual salaries and the issues involved with handling the bounty and reading into the code. $100 for a bug bounty is quite a lot already, but at codeweavers we have some estimation that fixing a minor bug costs about $1000 to $1500 to fix(http://www.codeweavers.com/services/engagements/) .
Sure, in a lot of cases the easiest way is to pay and get it done. Unfortunately not every person is able to offer hundreds of $ (as I am not).
So the most efficient way to get a bug fixed is to read into the code yourself.
I tried. I found function implementing GetAsyncKeyState but that's all I was able to do. Improveing this implementation was much over my little skills.
The bottom line is that while a free software project may be freely downloadable, but it is not a place where one can expect service for free.
I understand that and hope there wasn't anything wrong in my request. I tried be kind and ask for help, not demand it.