September 2006 - Wine-Devel

Clarification

by Tom Booker

Hi everyone, I feel like I owe some of you some clarification with all of the names I have slung around here in the past as my own.. I started contributing as Dustin Navea, then it switched to Dustin Booker, then to Tom Spear (aka Dustin Booker Dustin Navea), and finally to Tom Booker. It's about to change for the last time, to Tom Spear. My legal name was Dustin Thomas Booker until recently, Navea came from my stepfather, Spear was my mother's maiden name. Long story short, I prefer Tom to Dustin, so I flip flopped my first and middle name, and to honor my mother's father, and carry his family name on (he didn't have any sons), I decided to take his last name, so my legal name is Thomas Dustin Spear now, and it will (hopefully ;-) ) stay that way. Sorry for any confusion I may have caused in the past, including any this email may have caused. -- Thanks Tom Check out this new 3D Instant Messenger called IMVU. It's the best I have seen yet! http://www.imvu.com/catalog/web_registration.php?userId=1547373

Sept. 1, 2006

Re: Temporary Git tree available

by Saulius Krasuckas

Hello, Mike, * On Wed, 30 Aug 2006, Mike McCormack wrote: > As Alexandre has gone on holidays for a week, I've made available a > temporary Git tree containing most patches sent to wine-patches. Nice, thanks :) > You can pull my branch into your existing Git checkout as follows: > > git fetch http://mandoo.dyndns.org/wine.git master:mmbranch > git rebase mmbranch Could you, please, also attach gitweb interface to it and publish it? I know of no way to check "whatchanged -u" on a remote tree and also wouldn't like to pull mmbranch into my disk just for the current moment... In a case you have no references to gitweb: http://ehlo.org/~kay/?p=git/gitweb.git;a=blob;h=ea21fbe88a9455c80fd88f4f510…

Sept. 1, 2006

Re: Adding L"" defines to include files ?

by Frank Richter

On 01.09.2006 09:43, Paul Vriens wrote: > I've seen several occurrences of these in our own include files, so one > should think there is no harm. You could look how e.g. the WC_* macros are defined in commctrl.h. -f.r.

Sept. 1, 2006

Re: Adding L"" defines to include files ?

by Paul Vriens

On Fri, 2006-09-01 at 10:06 +0200, Marcus Meissner wrote: > On Fri, Sep 01, 2006 at 09:43:40AM +0200, Paul Vriens wrote: > > Hi, > > > > I'm currently dealing with the DllRegister part of wintrust. One of it's > > include files (softpub.h) on Windows has: > > > > #define SP_POLICY_PROVIDER_DLL_NAME L"WINTRUST.DLL" > > #define SP_INIT_FUNCTION L"SoftpubInitialize" > > #define SP_OBJTRUST_FUNCTION L"SoftpubLoadMessage" > > #define SP_SIGTRUST_FUNCTION L"SoftpubLoadSignature" > > #define SP_CHKCERT_FUNCTION L"SoftpubCheckCert" > > #define SP_FINALPOLICY_FUNCTION L"SoftpubAuthenticode" > > #define SP_CLEANUPPOLICY_FUNCTION L"SoftpubCleanup" > > > > should we do the same? > > > > I've seen several occurrences of these in our own include files, so one > > should think there is no harm. > > They won't work when used in WINE. > > L"xxx" usually gives a strings with 4 byte characters instead of the > expect 2. > > Ciao, Marcus > I'm only talking about the #defines. I've seen several cases in our code-base where we use these sort of defines (sometimes we needed to cast them when used). If we shouldn't use these, is it OK if I instead do something like: static WCHAR SP_POLICY_PROVIDER_DLL_NAME[] = {'W','I','N','T','R','U','S','T','.','D','L','L', 0}; but then not in the include file? Or should I then use a different name for the variable? Cheers, Paul.

Sept. 1, 2006

Re: Adding L"" defines to include files ?

by Marcus Meissner

On Fri, Sep 01, 2006 at 09:43:40AM +0200, Paul Vriens wrote: > Hi, > > I'm currently dealing with the DllRegister part of wintrust. One of it's > include files (softpub.h) on Windows has: > > #define SP_POLICY_PROVIDER_DLL_NAME L"WINTRUST.DLL" > #define SP_INIT_FUNCTION L"SoftpubInitialize" > #define SP_OBJTRUST_FUNCTION L"SoftpubLoadMessage" > #define SP_SIGTRUST_FUNCTION L"SoftpubLoadSignature" > #define SP_CHKCERT_FUNCTION L"SoftpubCheckCert" > #define SP_FINALPOLICY_FUNCTION L"SoftpubAuthenticode" > #define SP_CLEANUPPOLICY_FUNCTION L"SoftpubCleanup" > > should we do the same? > > I've seen several occurrences of these in our own include files, so one > should think there is no harm. They won't work when used in WINE. L"xxx" usually gives a strings with 4 byte characters instead of the expect 2. Ciao, Marcus

Sept. 1, 2006

Adding L"" defines to include files ?

by Paul Vriens

Hi, I'm currently dealing with the DllRegister part of wintrust. One of it's include files (softpub.h) on Windows has: #define SP_POLICY_PROVIDER_DLL_NAME L"WINTRUST.DLL" #define SP_INIT_FUNCTION L"SoftpubInitialize" #define SP_OBJTRUST_FUNCTION L"SoftpubLoadMessage" #define SP_SIGTRUST_FUNCTION L"SoftpubLoadSignature" #define SP_CHKCERT_FUNCTION L"SoftpubCheckCert" #define SP_FINALPOLICY_FUNCTION L"SoftpubAuthenticode" #define SP_CLEANUPPOLICY_FUNCTION L"SoftpubCleanup" should we do the same? I've seen several occurrences of these in our own include files, so one should think there is no harm. Cheers, Paul.

Sept. 1, 2006

Re: RFC: wine ASIO driver available for testing

by Andreas Mohr

Hi, On Thu, Aug 31, 2006 at 11:14:56PM -0400, Robert Reif wrote: > I just uploaded a simple wine ASIO driver to > http://bugs.winehq.org/show_bug.cgi?id=2161 for testing and feedback. Are you sure that those limited recipients were sufficient? (I don't think anyone here ever does a lot of ASIO app stuff) Might want to include http://linuxaudio.org/en/contact.html and http://ladspavst.linuxaudio.org/ people, too... Thanks for all your work on audio!! Andreas

Sept. 1, 2006

F.E.A.R. - free multiplayer

by EA Durbin

Since there was a discussion about getting F.E.A.R to work with wine on wine-devel the other day I thought I'd mention this link. http://www.fileshack.com/file.x/9272/F.E.A.R.+Combat+1.07 F.E.A.R. released the multiplayer portion of their game for free, you have to register on their site for a free cd key.

Sept. 1, 2006

RFC: wine ASIO driver available for testing

by Robert Reif

I just uploaded a simple wine ASIO driver to http://bugs.winehq.org/show_bug.cgi?id=2161 for testing and feedback. Please look at it and give me feedback. Playback works. Recording is untested due to lack of software. Full duplex doesn't work for me but I'm not sure if it's a software issue or a problem with my hardware and OS setup. The software is a long way from being ready for submission so any feedback or help would be appreciated.

Sept. 1, 2006

Thank you

by Jeremy White

We just shipped a public beta of CrossOver for the Mac. We're very excited about the Mac opportunities as we hope it will give us a much needed boost and allow us to accelerate our own contributions to Wine. I'm proud of our work on Wine - and I am very privileged to work with the folks at CodeWeavers. However, it's also clear that the Wine community is a growing one, and that a large portion of the work in CrossOver comes from people who contribute here. This past year, in particular, I've noticed a great jump in contributions, notably in the area of games (yay for World of Warcraft support!). By doing so, I think you make the world a better place, and indirectly you help all of us at CodeWeavers to make a living - you literally help to put food on my table (although my wife is getting tired of beans and rice :-/). So, thanks. I personally appreciate it, and think it's Good (TM) that you do. I also believe that countless other folks who use Wine in various forms also appreciate it, although they're polite enough not to write long winded emails expressing that. But for any of you that come to Reading, the least we can do is buy you dinner and a drink or two. And if any contributor ever needs something from CodeWeavers (like a free CrossOver account), just holler. Cheers, Jeremy White CEO CodeWeavers, Inc. p.s. Okay, being brutally honest, the jury is out on whether or not all the work making World of WarCrack^H^Hft is going to be a net gain for us or not. Now even my wife is addicted, and I have to go level up my Paladin to keep the work group happy... :-/

Sept. 1, 2006