September 2002 - Wine-Devel

Re: WineLib and DLLs (Winedump)
by steve.lustbader＠philips.com Sept. 25, 2002

Sept. 25, 2002

>> Does it matter that the dll is exporting C++ classes, not straight C >> functions? > >That could make things slightly more complicated, since MS and gcc use >different name mangling systems. if you declare functions with extern "C" >linkage you should be OK. However there are differences in how gcc and MS >call methods on objects (and in the vtable layout etc), so in general its not >advised to mix win32 c++ dlls with a winelib exe and vice versa (i.e you >should implement mydll.dll as a real wine dll rather than as just a stub for >linking). Actually, it's a win32 c++ app with lots of win32 c++ dlls and one winelib c++ dll. The winelib dll depends on two other win32 c++ dlls, which the app also depends on. I'm trying to avoid turning those other dlls into winelib dlls, since one of them uses ATL. Am I trying to do something that can't really be done? Is it possible to make the stub dll that winelib generates forward calls to the win32 dll (ie, give it both the gcc mangled name and the msvc mangled name)? -Steve

1 0

Re: d3d8 header patch.
by Dimitrie O. Paun Sept. 25, 2002

Sept. 25, 2002

On September 25, 2002 09:13 am, Yong Chi wrote: > I gave a .txt extension this time to make sure that the attachment got > treated as a text file. =) Excellent. But you didn't send it in the right format. Do cvs diff -u include/d3d8.h You should add diff -u to your .cvsrc file. -- Dimi.

2 1

another MZ_Exec() problem...
by chrismorgan＠rcn.com Sept. 25, 2002

Sept. 25, 2002

Inside of MZ_Exec() I call out to CreateProcessA() if the executable is PE. I've set the lpEnvironment parameter of CreateProcessA() to null to have it inherit the environment of the caller but this isn't working correctly. The path and other environment variables aren't being inherited. Ideas on how to either get CreateProcessA() to inherit properly or where I can find the environment settings? I noticed the env_ptr in the parmeter block but I'm unsure if this is what I'm looking for or where to find more information about it. Thanks, Chris

3 2

Re: d3d8 header patch.
by Uwe Bonnes Sept. 25, 2002

Sept. 25, 2002

>Hello! >I gave a .txt extension this time to make sure that the attachment got > treated as a text file. =) Now again as a unified diff (diff -u), and everybody is hapy :-) Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

1 0

how to declare COM class?
by Yong Chi Sept. 25, 2002

Sept. 25, 2002

Hello! I am one of those lurkers who finally decide to write code after many attempts. I declared a COM class best I can from looking at other COM class but I am getting syntax errors. I could not find any guide/manual on COM development. Can someone help or point to a guide on COM development? Thanks in advance...

4 4

Re: Listview Large Icon (LVS_ICON) rewrite.
by Dimitrie O. Paun Sept. 24, 2002

Sept. 24, 2002

On September 24, 2002 12:07 am, Guy L. Albertelli wrote: > This is a major rewrite of the LVS_ICON (large icon) code. Not everything > is working correctly yet. Known problems: > 1. Focus rectangles are left drawn incorrectly when scrolling window. I think I know what the problem is, I'll try to fix it. > 2. Background is incorrect for at least Outlook (white instead of grey). Hm, I don't have Outlook. Any pointers and/or ideas? > 3. Scrolling in Outlook is not correct. What's the problem with this one? I might be able to fix it... -- Dimi.

2 1

Re: [patch] Listview fixes
by Dimitrie O. Paun Sept. 24, 2002

Sept. 24, 2002

On September 24, 2002 05:43 pm, Paul Rupe wrote: > - Initialize memory to prevent crashes when -debugmsg +listview is on > + ZeroMemory(&lvItem, sizeof(lvItem)); Guys, *Please* stop adding these ZeroMemory calls! They just hide bugs, it is almost always the wrong fix (for the listview at least). Alexandre, you can apply the patch, I'll go through the ZeroMemory one more time anyway... -- Dimi.

1 0

ToDo's
by Thomas Wickline Sept. 24, 2002

Sept. 24, 2002

Hello, Here is the status of what I have so far on the ToDo's. I am not sure what section to put alot of this in so I just made Tools , Instructions & Aspect or Component for now. As much feedback as possiable is welcomed . Tom ----------------------- Wine ToDo's as of 9/24/02 Contact : twickline2(a)triad.rr.com Wine ToDo OverView Window management * Window management needs proper inter-process handling of activation, focus, repaint. National Language Support * ASCII function work Winsock * Winsock1 calls,in particular select(),use direct system calls instead of using related wine APIs * More unit tests need to be written * Make sure OOB data is handled properly. Check client-size blocking. * WS2: "provider" interface * WS2: Support other kind of services, like IrDA. * Fix stubs left in ws2_32.spec Multimedia wave audio * Open Sound System: Support for full-duplex. Fix bugs. * Drivers for other APIs (ALSA, Esound, others). DirectSound * Make the latency configurable (tunable). * More intelligent prebuffering. * Complete support for hardware secondary buffers through the HAL (for a future ALSA multimedia wave audio driver). * 3D sound buffers. * Sound capture (recording). Tools * wine installation process should install and configure wine * winemaker fixes * Run C regression tests on Windows with MSVC * Compile Wine with -DSTRICT * Work on WRC as it does not find system headers Instructions * Write a proper Users Guide Introduction * Documentation updates Aspect or Component * More DLL Separation * BiDi support * Review of Wine Server Protocol * Finalize Server Protocol * VxD support * PAM (Pluggable Authentication Modules) * SEH support * Visual C++'s native COM support * Complete the SMB code (Server Message Block) * Implement WinNT file handling * Add DWARF2 support * Implement a DIB engine * Speed up PDB support * Network UNC path handling * Libfontconfig support * Create replacement of browser component (Internet Explorer/I Add links to: Tasklets: http://bugs.winehq.com/buglist.cgi?keywords=tasklet tasklist: http://bugs.winehq.com/buglist.cgi?keywords=tasklist For a full list of .9/1.0 task's

2 1

RFC: Winsock todo's
by Martin Wilck Sept. 24, 2002

Sept. 24, 2002

This is a RFC for comments. I may currently be the "offical" winsock maintainer in wine, but I wrote only a very small part of the code. I invite everybody, especially the authors of the other parts of winsock, to comment on these opinions. On Son, 2002-09-22, 18.48 Thomas Wickline wrote: > Can you give me a update on winsock todo's ? > And any other todo that you are aware of .. I have received very few bug reports lately, so I guess the basic Winsock functionality is working. A few important patches went in after the latest CVS snapshot, though. In general, the Winsock implementation in wine has a few parts that look really hackish and would need substantial cleanup. IMO this applies to the async.c file in total, but maybe I am doing injustice to authors of that file. I just find the code is really hard to read. Things like the User-space callbacks in WSAAccept() are impossible to implement correctly because the Unix accept() system call doesn't support callbacks. I do not like the fact that some Winsock1 calls, in particular select(), use direct system calls instead of using related wine APIs, e.g. WaitforMultipleEvents(). Actually if you have sockets with overlapped IO this may cause havoc. Changing this seems to be an average-difficulty task, suitable for contributors with some insight into wine internals. I'd like to see this fixed before 1.0. There are quite a few stubs left in ws2_32.spec. Some of these can probably be implemented easily and would be good work for beginners or casual wine contributors looking for a simple task, e.g. WSADuplicateSocketW(), WSAAddressToString[AW], WSAHtonl(). More unit tests need to be written, also a nice task for people interested in Winsock. Wine has no concept of the Winsock2 "provider" interface. All calls to these functions are either stubs or dummy functions, such as WSAEnumProtocols(). I had a patch for this, but never got it ready for prime-time. It is unrealistic to support a "real" provider interface, allowing (like Windows) to hook new protocol handlers in the network stack, but at least we should pass some realistic information to clients. Should be done for 1.0. There is no such thing as a QOS or socket group concept in wine either, but these seem to be rarely-used features -> post-1.0, if needed at all. Although I had a relevant part in implementing the asynchronous IO in winsock, I am not quite content with it because it is not really asynchronous. Alexandre is against using threads. On Linux at least, Ben LaHaise's asyncio can be expected to become part of the 2.6 kernel series, and if that happens the wine asynchronous IO functionality should be rewritten to use the asyncio API on systems that support it. (I still havent't figured out whether aio will support sockets, though). A non-winsock todo that comes to my mind is support for NT security concepts such as tokens. But that would be a big one and should probably also be postponed after 1.0 Martin -- Martin Wilck Phone: +49 5251 8 15113 Fujitsu Siemens Computers Fax: +49 5251 8 20409 Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck(a)Fujitsu-Siemens.com D-33106 Paderborn http://www.fujitsu-siemens.com/primergy

2 2

Re: Edit updates
by Dimitrie O. Paun Sept. 24, 2002

Sept. 24, 2002

On September 24, 2002 02:09 am, Dimitrie O. Paun wrote: > This patch is trying to bring the edit.c in line > with the other controls. There is a problem with this patch, please don't apply. -- Dimi.

1 0