Re: Three year sever outstanding bug requiring minor fix
On 12 June 2010 00:23, Aneurin Price wrote: > Is it a legal requirement that everyone working on WINE must be a > complete arsehole, or just a project requirement? > > Nye Which side are you on? Peter
Re: Three year sever outstanding bug requiring minor fix
Is it a legal requirement that everyone working on WINE must be a complete arsehole, or just a project requirement? Nye
Re: Three year sever outstanding bug requiring minor fix
On Wed, Jun 9, 2010 at 12:52 PM, velociraptor Genjix wrote: > Hey, > Please look into this issue, > http://bugs.winehq.org/show_bug.cgi?id=15118 > It seems like a fairly trivial fix which renders this application useless. A > detailed description of the implementation needed is provided in that > ticket. > Thank you Seriously. I fail to see how you can find the fix "easy". I've read the problem description and it doesn't appear to be easy at all. How is Wine supposed to support transparent windows? With Compiz? With the Composite extension? How to check for them? What if they are not available? Yes, one could just set the appropriate xatom flags and be done with it, but if a compositing window manager is not present it won't do anything. Also, I am not sure about the click through flag, that would require some spelunking to find out how wine supports it, if at all. All in all, it doesn't appear to be trivial. It doesn't even have a proposed patch! Repeating assertions in the bug report and the mailing list is a good way to annoy people. One thing that you should understand is that "widely wanted features" mean exactly nothing. Being "widely wanted" won't make the feature easier to implement, test or integrate. You could offer a business proposition to CodeWeavers or Transgaming, for them to implement a feature, offer a bounty, code it yourself or even pay someone you know to do it for you. You could even work with other people in UK who like playing poker to pool the resources for such task. That would be more productive. -- Stephen Sent from my Emacs
RE: Three year sever outstanding bug requiring minor fix
Hey, Sorry I didn't mean any offence caused. It's just I saw that the new wine release is going to fix bugs and tried to bring it to your attention. I saw the guy Will Tipton in that bug ticket provided a detailed analysis of the problem so it looked easy since you already would know the problem (or at least a lot less difficult). Not only that but it has 9 votes and is a widely wanted asked for feature if you check google, http://www.google.co.uk/search?sourceid=chrome&ie=UTF-8&q=pokertracker+wine I didn't mean to be making people upset, it was more a helpful suggestion. Maybe caused by english language being not my first. > Date: Wed, 9 Jun 2010 11:00:16 -0700 > From: jjmckenzi...@earthlink.net > To: wine-devel@winehq.org > Subject: Re: Three year sever outstanding bug requiring minor fix > > velociraptor Genjix wrote at Jun 9, 2010 8:52 AM > > > >Hey, > >Please look into this issue, > >http://bugs.winehq.org/show_bug.cgi?id=15118 > >It seems like a fairly trivial fix which renders this application useless. A > >detailed > >description of the implementation needed is provided in that ticket. > > If it were a 'trival' fix, it would have been a long time ago. Something > that looks, on the surface, to be simple, maybe very complex. For instance, > I have been working on a fix for one function in the richedit area has taken > over four years. > > Now as to your concern, tough. This project, for the most part is volunteer. > So, if you want it fixed, do it yourself or find someone who can. > Otherwise, you'll have to wait for someone to come by, find this interesting > and then fix it. There is a part of the project that is paid, and they work > for a company called CodeWeavers. Maybe they have found a fix and > incorporated it into their product line. That you'll have to pay for. > > Remember, we fix things as WE find the time and the incorporation process is > very strict. This takes time and some folks will pick up a project, only to > set it down because they become busy with other things in life or they just > don't have the tenancity to see it through. > > James McKenzie > > > _ http://clk.atdmt.com/UKM/go/19780/direct/01/ We want to hear all your funny, exciting and crazy Hotmail stories. Tell us now
Re: Three year sever outstanding bug requiring minor fix
velociraptor Genjix wrote at Jun 9, 2010 8:52 AM > >Hey, >Please look into this issue, >http://bugs.winehq.org/show_bug.cgi?id=15118 >It seems like a fairly trivial fix which renders this application useless. A >detailed >description of the implementation needed is provided in that ticket. If it were a 'trival' fix, it would have been a long time ago. Something that looks, on the surface, to be simple, maybe very complex. For instance, I have been working on a fix for one function in the richedit area has taken over four years. Now as to your concern, tough. This project, for the most part is volunteer. So, if you want it fixed, do it yourself or find someone who can. Otherwise, you'll have to wait for someone to come by, find this interesting and then fix it. There is a part of the project that is paid, and they work for a company called CodeWeavers. Maybe they have found a fix and incorporated it into their product line. That you'll have to pay for. Remember, we fix things as WE find the time and the incorporation process is very strict. This takes time and some folks will pick up a project, only to set it down because they become busy with other things in life or they just don't have the tenancity to see it through. James McKenzie
Re: Three year sever outstanding bug requiring minor fix
Hello Fakename, 2010/6/9 velociraptor Genjix : > Hey, > Please look into this issue, > http://bugs.winehq.org/show_bug.cgi?id=15118 > It seems like a fairly trivial fix which renders this application useless. A > detailed description of the implementation needed is provided in that > ticket. > Thank you Wine is run by volunteers, you cannot tell others what to do since they work on wine voluntary. If you want the bug fixed, your best bet is to try to fix it yourself. We can likely help you if you can program in C, but just posting 'please fix this bug for me' is rude and selfish. Cheers, Maarten