April 2004 - Wine-Devel - list.winehq.org

Re: Handling dialogs created without using templates

by Dmitry Timoshkov

"Santosh Siddheshwar" <santosh.s(a)sonata-software.com> wrote: > Thanks. Would you be able to share details of the changes you did for > handling MDI windows? The patch is here: http://cvs.winehq.com/patch.py?id=10783 I think that (almost) all that needs to be done about the problem is to move most of the DIALOG_CreateIndirect to WM_CREATE handler in DefDlgProc, including setting of WIN_ISDIALOG, i.e. just slightly rearrange dialog initialization code. -- Dmitry.

April 5, 2004

Re: Re: dbghelp

by Pouech Eric DMI AEI CAEN

> UnDecorateName is still a stub, while our winedump has some a good > framework for UnDecorateName, also translating into a GCC way and not in a > VC++ way. How should these things go together? See the comment in dbghelp.c !! My first thouhgt would be to make a .a lib out of winedump code, and use it in winedump and msvcrt and / or dbghelp. I haven't studied yet the best way to share the code between msvcrt and dbghelp A+

April 5, 2004

RE: Handling dialogs created without using templates

by Santosh Siddheshwar

Hi, Thanks. Would you be able to share details of the changes you did for handling MDI windows? Regards Santosh > -----Original Message----- > From: Dmitry Timoshkov [SMTP:dmitry(a)baikal.ru] > Sent: Tuesday, March 30, 2004 7:40 PM > To: Santosh Siddheshwar > Cc: wine-devel(a)winehq.com > Subject: Re: Handling dialogs created without using templates > > "Santosh Siddheshwar" <santosh.s(a)sonata-software.com> wrote: > > > Yes attached is a sample which is pretty similar to what I described > > below. > > Thanks. Now I see where the problem is. We have to hook dialog creation > code into common window creation code, something similar to what I've done > recently for MDI. Alexandre, are my thoughts correct? > > -- > Dmitry. ********************************************************************* Disclaimer: The information in this e-mail and any attachments is confidential / privileged. It is intended solely for the addressee or addressees. If you are not the addressee indicated in this message, you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind. *********************************************************************

April 5, 2004

Re: appdb - improvement in serching out bugs

by hatky

> No, no, no... read the patch again. Ok, sorry wasn't what I tought you are trying to do, this patch is ok p.s. I didn't think someone actually changed the urls in bugzilla. sweet :). -- Hatky, Worshiper of wine (http://www.winehq.org/) Impossible is only an opinion.

April 5, 2004

Re: Should winemaker be able to handle this

by Dimitrie O. Paun

On April 3, 2004 6:43 pm, Francois Gouget wrote: > I agree on the A/B distinction. However even in the B case we need these > options for those cases where winemaker generates a whole lot of > makefiles. Right. We need to support that case, but it seems that we need a way to include stuff in the generated Makefiles. So, instead of adding all these options, maybe we can find a way to simply allow the user to include stuff in the generated Makefile. Something simple, like: winemaker -A 'DEFS=-DSTRICT ...' where -A will simply add the argument as a line at the beginning of the generated Makefile. This is easier to implement, document, etc., and it's general enough that we don't have to keep adding options to support all sorts of users. -- Dimi.

April 5, 2004

Re: WININET: move to Windows sockets

by Dimitrie O. Paun

On April 4, 2004 10:18 pm, Jonathan Wilson wrote: > Use #ifdef stuff so that when building on WINE, it uses unix sockets. We have to be smart about this, having #ifdefs all over the file is not acceptable. But from the look of the patch that was just posted, it certainly looks like we can achieve this without too much pain. But yes, I'm also curious how much of a hit we're taking. -- Dimi.

April 5, 2004

Re: WININET: move to Windows sockets

by Jonathan Wilson

How about this. Use #ifdef stuff so that when building on WINE, it uses unix sockets. But when building on win32 (which would include MingW and ReactOS), it uses winsock.

April 5, 2004

Re: WININET: move to Windows sockets

by Steven Edwards

Hello Hans, --- Hans Leidekker <hans(a)it.vu.nl> wrote: > > This makes wininet build on MinGW. > > Changelog: > Move to Windows sockets. > I asked Alexandre about a patch to move Wininet to Winsock and he said it took to much of a performance hit to merge. Is there a way we can bench mark it to show how much of a hit Winsock vs Unix sockets is going to give us? He suggested that we find a way to make Wininet use Unix sockets on Unix and Winsock on Windows. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/

April 5, 2004

Re: DDraw issues, etc.

by Francois Gouget

On Sun, 4 Apr 2004, Tim Hentenaar wrote: [...] > 00:1f.5 Multimedia audio controller: Intel Corp. 82801BA/BAM AC'97 Audio (rev 05) [...] > Hmm.. I don't believe that my card is an i810, it could be, but I have > the alsa drivers statically linked into my kernel and I forgot exactly > which one it is. It looks like an i810 to me (but I have never actually seen one so...) Do you know if it is integrated on the motherboard? And then is it an Intel chipset? Also, cat /proc/asound/cards will tell you what type of sound card you have. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ If it stinks, it's chemistry. If it moves, it's biology. If it does not work, It's computer science.

April 5, 2004

Re: DDraw issues, etc.

by Tim Hentenaar

On Mon, 5 Apr 2004 02:20:51 +0200 (CEST) Francois Gouget <fgouget(a)free.fr> wrote: > It looks like an i810 to me (but I have never actually seen one so...) > > Do you know if it is integrated on the motherboard? And then is it an > Intel chipset? > > Also, cat /proc/asound/cards will tell you what type of sound card you > have. 0 [I82801BAICH2 ]: ICH - Intel 82801BA-ICH2 Intel 82801BA-ICH2 at 0x1200, irq 10 apparently it's an ICH2 and not an i810, and yes it is integrated on the motherboard. (My computer is a laptop :P) The odd thing about it is that the sound works fine in WineX (after a little hacking to get it to even run the app :/). Tim

April 5, 2004