wine-devel

wine-devel@winehq.org

2 participants
84469 discussions

Re: Small make compatibility changes (take 2)
by Alexandre Julliard 11 Aug '04

11 Aug '04

Vincent Béron <vberon(a)mecano.gme.usherb.ca> writes: > This seems to let users build and uninstall with BSD make. > > Changelog: > Evaluate variable after replacement to build with BSD make. Unfortunately assignments with := are not portable either, so it's only moving the problem. We probably need to restructure the makefiles a bit to avoid that construct. -- Alexandre Julliard julliard(a)winehq.org

3 4

Help with winemaker
by Veerendra Tippanagoudar 11 Aug '04

11 Aug '04

Hi, I am trying to port a project from windows to unix. I have installed redhat 7.0. After installing wine, i tried using winemaker on a set of modules that are interdependent. By modules, I mean sub-programs. When I run winemaker from the top of the project directory, it creates only Makefile and no configure, configure.in and Makefile.in scripts. Therefore I am not able to use ./configure --with-wine=/usr/local/wine. Since, I cannot run the ./configure command, I am not able to run the make command. Why are the configure and other files not being generated? Any help would really be appreciated. My project uses, C and C++ code. Thank you, Veerendra Tippanagoudar. P.S: The documentation online is not complete (especially the Makefile.in and Configure.in part). --------------------------------- Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage!

2 1

Re: USB?
by Rolf Kalbermatter 11 Aug '04

11 Aug '04

Aric Stewart wrote: >I do have some difficulty figuring out how win2k is translating vender >and product ids into class and interface guids. The documentation >reports that they look them up in inf files, however i am finding that >not to be true. I am suspecting that some may be hardcoded in the usb >support somewhere. Wouldn't that be something which would be put in the registry somehow for the well known IDs and for the rest I really assume the device detection routine does check for all .inf files it finds on the devices currently configured to be searched. If you look at PCI and USB inf files you will notice that the manufacturer and device ID are actually encoded in the key names which are to be added to the registry. That encoding does not always seem to be equally consistent, I've seen at least two different types, but it is obviously there. One entry for instance for the Logitec PageScanner would be %USB\VID_046D&PID_040f.DeviceDesc%=Model.PageScan_USB,USB\VID_046D&PID_040f USB\VID_046D&PID_040f.DeviceDesc="Storm Technology - Logitech PageScan USB" This is partly extracted from a logiscan.inf file on my W2K system. Rolf Kalbermatter

2 1

winedbg doesn't find source files
by Saulius Krasuckas 11 Aug '04

11 Aug '04

When using CVS version of Wine I cannot get much debug: [s2@katleriai Spawn]$ WINEDEBUG=+volume winedbg winecfg fixme:console:SetConsoleCtrlHandler (0x4066a644,1) - no error checking or testing yet WineDbg starting on pid 0xa In 32 bit mode. Unable to open file /process.c Wine-dbg>br GetDriveTypeW fixme:dbghelp:elf_lookup_symtab Already found symbol add_paint_count (/usr/src/wine-cvs/wine/dlls/user/../../windows/painting.c) in symtab painting.c @00074738 and painting.c @000a026c fixme:dbghelp:elf_load_debug_info Unsupported Dwarf2 information Breakpoint 1 at 0x403be249 GetDriveTypeW [volume.c:1418] in kernel32 Wine-dbg>c fixme:winecfg:WinMain The winecfg tool is not yet complete, and does not actually alter your configuration. fixme:winecfg:WinMain If you want to alter the way Wine works, look in the ~/.wine/config file for more information. trace:volume:GetVolumeInformationW cannot open device L"\\\\.\\C:": err 2 Stopped on breakpoint 1 at 0x403be249 GetDriveTypeW [volume.c:1418] in kernel32 Unable to open file volume.c Wine-dbg>list 10 Wine-dbg>quit WineDbg terminated on pid 0xa I have had a long period of time not using the winedbg, so I cannot tell whether it is a regression. I am using "./configure && make depend && make" to build the Wine and then something like a "sudo make install", if that matters. I need an advice on how to setup winedbg the right way or an explanation, whether this is a bug or an advanced feature. TIA.

3 5

no scrollbar with native comctl
by Nicolai Kuntze 11 Aug '04

11 Aug '04

Hi, I have tried my bug (2302) with mostly every dll in the native version. But the scrollbars are unvisible. The programm works fine under Windows. Can someone help me? Nicolai ---- Diese Nachricht wurde auf Viren und andere gefaehrliche Inhalte sowie Spam untersucht.

1 0

responses
by Patrick C McKelvey 11 Aug '04

11 Aug '04

I am responding to the italicized note in the user manual (pdf). 1) Your early adopters probably do not look at the user manual any more. 2) Having written some documents like this, I do not believe that most people realize how difficult it is to make a process simple and clear without making it insulting. A company I used to work for had a 5 day course on writing user manual and procedures that they marketed nation wide. I do not know if the still do so. I went through that course and it was amazingly difficult. All you need to do is write down what to do and no one will understand you. 3) Those who are into Linux are into the bleeding edge of technology and want to make it run, not tell others how to make it run. An audience of true nerds, and I will raise my hand, will like to see the thing work. Documentation is in last place. I appreciate what you run into on the thankless task of documentation and keeping it current. My guess is that this is the one thing that is the major weak spot in Linux. If anything except perhaps support, will kill Linux, it will be lousy documentation. Having been a Unix system administrator for a long while, I have seen great systems go away because of documentation or support. Legato nearly went under because of support. The system is good, I chose it to back up 25 production Unix boxes into a tape silo over a 1G fiber network. After I left, I understand they went with another system because they could no longer get any answers to their questions and the documentation was not clear. I am retired on disability now. I have heard rumors that Legato has turned the problems around and is recovering some of it's lost market share. I have just started trying to use Wine on Fedora Core2 and I will be reading all the documentation. What I have seen so far has been well done. I will be finding out if it still applies, and applies to Quicken 2004 Deluxe. Sincerely yours, Patrick C. McKelvey PE Cincinnati, Ohio pmckelvey(a)zoomtown.com

1 0

dosmem: MCB implementation
by markus.amsler＠oribi.org 11 Aug '04

11 Aug '04

Hi, I'm trying to run freecom[1] of the freedos project in wineconsole. After changing comspec in user.reg and some ugly hacks to kernel/dosmem.c it runs (dosmem_paragraph.patch). But it will never run cleanly without proper MCB support (it does its own MCB-chain walking, like a lot of other programms). I tried to implement it (dos_mcb.patch also ugly), and now i have some design questions: - where to implement MCB's? kernel or winedos? (the PSP from winedos is needed to write the MCB and the first MCB is needed in winedos DOS_LOL[2]) - how to get rid of the separtion hack of DOSMEM[3] - what about the use of DOSMEM in global16.c, do they need also MCB's (found no docu about the GA_DOSMEM flag) Markus [1] http://freedos.sourceforge.net/freecom/FreeCOM.html [2] http://source.winehq.org/source/dlls/winedos/devices.c#L478 [3] http://source.winehq.org/source/dlls/kernel/kernel32.spec#L1164

3 5

Dockable Toolbar painting issue on SUSE 9.1
by Krishna Murthy 10 Aug '04

10 Aug '04

I am facing the following issue on SUSe pro 9.1, but this issue is not happening on RH 9.1. - The MFC application has the dockable toolbar - When I undock the toolbar to display ad popup window, the screen is not refreshed and when I see the trace, the X11DRV_SetWindowPos() is called ininitely. - Any one faced this issue? - Could you please point me to the wine code source files related to toolbar / dockable controls so that I could debug where the problem is occurring. The SUSe pro 9.1 has the follwoing library versions: XFree86-fonts-scalable-4.3.99.902-40 XFree86-libs-4.3.99.902-40 XFree86-Mesa-devel-4.3.99.902-40 XFree86-fonts-75dpi-4.3.99.902-40 XFree86-4.3.99.902-43.25 XFree86-Mesa-4.3.99.902-40 XFree86-devel-4.3.99.902-40 XFree86-server-glx-4.3.99.902-40 XFree86-server-4.3.99.902-43.25 XFree86-Xvnc-4.3.99.902-40 kdebase3-SuSE-9.1-18.1 kdebase3-3.2.1-68.15 Thanks in advance, Krishna Murthy Gupta Technologies LLC TEL: (650) 596-4828 E-mail: Krishna.Murthy(a)guptaworldwide.com

1 1

RE: Wine devel: Two MFC bugs
by Green, Shaun E. 10 Aug '04

10 Aug '04

>This is a known problem. Our edit control does not currently support the ES_RIGHT style at this time. Okay, thanks for letting me know. > The second bug is that when I multi-select files to perform an > operation on, nothing happens. One selected file works fine, but any > additional ones cause nothing to happen. Works fine in Windows. >What control are you using for the multi-select? ofn.Flags = OFN_ALLOWMULTISELECT | OFN_HIDEREADONLY | OFN_FILEMUSTEXIST | OFN_EXPLORER ; Here is the dialog code; szFileName[0] = '\0'; OPENFILENAME ofn; ofn.lStructSize = sizeof (OPENFILENAME); ofn.hwndOwner = this->m_hWnd; ofn.hInstance = NULL; #if _LANGUAGE==FRENCH ofn.lpstrFilter = "Fichiers TXT\0*.txt\0\0"; #elif _LANGUAGE==ENGLISH ofn.lpstrFilter = "txt (*.txt)\0*.txt\0\0"; #endif ofn.lpstrCustomFilter = NULL; ofn.nMaxCustFilter = 0; ofn.nFilterIndex = 0; ofn.lpstrFile = szFileName; ofn.nMaxFile = _MAX_PATH+50000; ofn.lpstrFileTitle = NULL; ofn.nMaxFileTitle = 0; ofn.lpstrInitialDir = pDoc->repertoire; ofn.lpstrTitle = NULL; ofn.Flags = OFN_ALLOWMULTISELECT | OFN_HIDEREADONLY | OFN_FILEMUSTEXIST | OFN_EXPLORER ; ofn.nFileOffset = 0; ofn.nFileExtension = 0; ofn.lpstrDefExt = NULL; #ifdef _DEBUG ofn.lCustData = 1L; #else ofn.lCustData = 0L; #endif ofn.lpfnHook = NULL; ofn.lpTemplateName = NULL; if (GetOpenFileName (&ofn)) { Thanks, Shaun

2 1

Incoming message
by Prupe 10 Aug '04

10 Aug '04

1 0

Wine devel: Two MFC bugs
by Green, Shaun E. 10 Aug '04

10 Aug '04

I would like to first thank all the Wine developers for your help. Without you, this wonderful software would not be maintained and allow good cross-platform app development. Several months ago I received some help from the list on an MFC application I'm helping develop. Now that I've completed sokoban version 1.3, I'm ready to report only two bugs I've found with the latest Wine 20040716, running the sokoban.exe in Linux. The first is a display problem of edit boxes; for some reason the text (numbers) are displaying left justified, instead of right justified. The edit boxes are definitely set for right justified and display fine in Windows. The second bug is that when I multi-select files to perform an operation on, nothing happens. One selected file works fine, but any additional ones cause nothing to happen. Works fine in Windows. For both of these problems I'd be happy to provide the MFC/C++ code snippets, just let me know. Thanks, Shaun

2 1

(no subject)
by Dpaun 10 Aug '04

10 Aug '04

1 0

Re: Wine devel: Two MFC bugs
by Dan Kegel 10 Aug '04

10 Aug '04

Shaun Green wrote: > The first is a display problem of edit boxes; for some reason the text > (numbers) are displaying left justified, instead of right justified. The > edit boxes are definitely set for right justified and display fine in > Windows. > > The second bug is that when I multi-select files to perform an operation on, > nothing happens. One selected file works fine, but any additional ones cause > nothing to happen. Works fine in Windows. > > For both of these problems I'd be happy to provide the MFC/C++ code > snippets, just let me know. Please do. Ideally, you should file a separate bug in Wine's bugzilla (http://bugs.winehq.org/) for each of the two problems, and attach or link to a zip file of an MSVC project plus source code and executable of the small test case. (Like I did in bug http://bugs.winehq.org/show_bug.cgi?id=1404 ) Thanks, Dan -- My technical stuff: http://kegel.com My politics: see http://www.misleader.org for examples of why I'm for regime change

1 0

Winelib under Solaris/SPARC
by Robin KAY 10 Aug '04

10 Aug '04

I would to like compile Winelib under Solaris/SPARC so that I can develop Windows applications from the relative comfort of UNIX, leaving only the final building and testing to real Windows running under Bochs. I have tested a selection of Wine releases and the build typically fails with either one of two errors. I used gcc 3.3.4 with the assembler and linker from binutils 2.15, and I configured the builds with: LDFLAGS="-R/opt/csw/lib -L/opt/csw/lib" CPPFLAGS="-I/opt/csw/include" ./configure --without-opengl 1) Releases between wine-20021125 and wine-20040121 (inclusive) gcc -c -I. -I. -I../../include -I../../include -I/usr/openwin/include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -gstabs+ -Wpointer-arith -I/opt/csw/include -g -O2 -o ddraw.spec.o ddraw.spec.c {standard input}: Assembler messages: {standard input}:1169: Error: operation combines symbols in different segments [snip] {standard input}:2006: Error: operation combines symbols in different segments gmake[2]: *** [ddraw.spec.o] Error 1 An archived mailing list post suggested that this is caused by a failure to RTFM and configure the source tree to build winelib rather than plain wine with PE loader, however I haven't been able to find any documentation that supports this view. None of the releases I tested had a configure script which accepted --disable-emulator. The source file which causes this error varies with release. 2) Releases between wine-20040213 and wine-20040716 (inclusive) ../../tools/winegcc/winegcc -B../../tools/winebuild -shared ./ntdll.spec cdrom.o critsection.o debugbuffer.o debugtools.o directory.o env.o error.o exception.o file.o heap.o large_int.o loader.o loadorder.o misc.o nt.o om.o path.o process.o reg.o relay.o resource.o rtl.o rtlbitmap.o rtlstr.o sec.o server.o signal_i386.o signal_powerpc.o signal_sparc.o string.o sync.o version.o thread.o time.o virtual.o wcstring.o relay32.o ntdll.dll.dbg.o -o ntdll.dll.so -L../../dlls -L../../libs/wine -lwine -L../../libs/unicode -lwine_unicode -L../../libs/port -lwine_port -R/opt/csw/lib -L/opt/csw/lib -lresolv -lsocket -lnsl ntdll.dll-DqmZVz.spec.c:20:1: warning: "__stdcall" redefined <command line>:17:1: warning: this is the location of the previous definition thread.o(.text+0xc1c): In function `NtCurrentTeb': /home/komadori/dev/stuff/wine-20040716/dlls/ntdll/thread.c:582: undefined reference to `wine_pthread_get_current_teb' collect2: ld returned 1 exit status winegcc: gcc failed. gmake[2]: *** [ntdll.dll.so] Error 2 I tried adding wine_pthread_get_current_teb to libs/wine/wine.def and libs/wine/wine.map, but this caused the resulting binaries to dereference a bad address in NtCurrentTeb. This mail was origianally posted to comp.emulators.ms-windows.wine from where I was redirectled. Does anyone know how to fix these problems or if any of the older release tags in CVS will build under Solaris/SPARC? Thanks. -- Wishing you good fortune, --Robin Kay-- (komadori)

2 2

Problem with ITypeInfo
by jack 10 Aug '04

10 Aug '04

Hi. I've tryed to run game Project Entropia and I got segmentation fault because of a bug in OLE. I've hacked code and I found two bugs: 1. ITypeInfo has back pointer to ITypeLib, but it's possible (and happened) that ITypeLib is destroyed and later ITypeInfo calls its function. I've solve this problem by call ITypeLib_AddRef while creating ITypeInfo (and ITypeLib_Release while destroying ITypeInfo). 2. ITypeInfo_Invoke doesn't support optional parameters. I've added support for cParamsOpt>0. MSDN says that optional parameter is when VARTYPE equals VT_EMPTY, but in my case it was a VT_BYREF | VT_VARIANT type but the pointer was NULL. When I treated it as VT_EMPTY, it was OK. I enclose my patch. My knownlage about OLE is sparse so I'm not able to test this. Thanks, Jacek

3 4

Re: Add a linker rpath so libwine can be found without modifying ld.so.conf or LD_LIBRARY_PATH
by Alexandre Julliard 09 Aug '04

09 Aug '04

Mike Hearn <mike(a)navi.cx> writes: > --- Make.rules.in.~1.172.~ 2004-03-24 03:34:01.000000000 +0000 > +++ Make.rules.in 2004-08-02 22:57:38.868759456 +0100 > @@ -78,6 +78,7 @@ > LIBPORT = -L$(TOPOBJDIR)/libs/port -lwine_port > LIBUNICODE = -L$(TOPOBJDIR)/libs/unicode -lwine_unicode > LIBWINE = -L$(TOPOBJDIR)/libs/wine -lwine > +RPATH = -Wl,-rpath,'$${ORIGIN}/../lib' You cannot depend on libdir being ../lib, users can specify a different one. -- Alexandre Julliard julliard(a)winehq.org

1 0

CVS build fails
by Ivan Leo Puoti 09 Aug '04

09 Aug '04

Current CVS build fails. make[3]: Entering directory `/home/ivan/Development/Wine/CVS/wine/wine/dlls/winmm/tests' gcc -c -I. -I. -I../../../include -I../../../include -D_REENTRANT -fPIC -Wall -pipe -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o mixer.o mixer.c mixer.c: In function `mixer_test_deviceA': mixer.c:353: error: union has no member named `s1' mixer.c:354: error: union has no member named `s1' mixer.c: In function `mixer_test_deviceW': mixer.c:570: error: union has no member named `s1' mixer.c:571: error: union has no member named `s1' make[3]: *** [mixer.o] Error 1 make[3]: Leaving directory `/home/ivan/Development/Wine/CVS/wine/wine/dlls/winmm/tests' make[2]: *** [tests] Error 2 make[2]: Leaving directory `/home/ivan/Development/Wine/CVS/wine/wine/dlls/winmm' make[1]: *** [winmm] Error 2 make[1]: Leaving directory `/home/ivan/Development/Wine/CVS/wine/wine/dlls' make: *** [dlls] Error 2 [ivan@localhost wine]$ Ivan.

1 0

Re: RSABASE/TESTS: Fix signed/unsigned comparison warnings
by Dmitry Timoshkov 09 Aug '04

09 Aug '04

"Hans Leidekker" <hans(a)it.vu.nl> wrote: > +static const int size_of_wchar = sizeof(WCHAR); > + ... > - ok(!memcmp(bufW, stringW, 5 * sizeof(WCHAR)), "bufW/stringW mismatch\n"); > + ok(!memcmp(bufW, stringW, 5 * size_of_wchar), "bufW/stringW mismatch\n"); > - if (GetLastError()==NTE_BAD_KEYSET) > + LONG gle = GetLastError(); > + if (gle==NTE_BAD_KEYSET) This is ugly. This kind of "fixes" clutters Wine code and should be deprecated. -- Dmitry.

3 4

rsabase and itunes
by Michael Jung 09 Aug '04

09 Aug '04

Rob, I've seen the press release concerning the CrossOver Office iTunes preview and I've noticed that it depends on libcrypto. Im just wondering if your effort with rsabase is related to this? Greetings, Michael -- Michael Jung, MSc Be liberal in what you accept, Integrated Circuits and Systems Lab and conservative in what you send. University of Technology, Darmstadt -- Jonathan Postel, Internet Pioneer phone: +49(6151)16-6692 / email: mjung(a)iss.tu-darmstadt.de

2 1

"Call Identifier" -- MSRPC ??
by Auge Mike 09 Aug '04

09 Aug '04

Hi all, I really like to know hot to change the "call identifier" in a MSRPC call??? Please help me, I already wasted too long time searching for this info with no luck??? Thank you in advance!!! _________________________________________________________________ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail

1 0

Re: Add debugstr_rect alias for consistency with other debugging functions.
by Alexandre Julliard 08 Aug '04

08 Aug '04

Mike Hearn <mike(a)navi.cx> writes: > The lack of this confused me for a few minutes, might as well stick it in. It's missing because it violates namespace rules. The other debugstr functions are here for historical reasons but we shouldn't add new ones. -- Alexandre Julliard julliard(a)winehq.org

3 3

Re: Fix crash in dsound test
by Ferenc Wagner 08 Aug '04

08 Aug '04

Paul Millar <paulm(a)astro.gla.ac.uk> writes: > The build failed. It looks like there's a bug in CVS. Both > CLSID_DirectSoundPrivate and DSPROPSETID_DirectSoundDevice defined multiple > times (the wine-version of mingw libraries and in the source). Yes, there was a short discussion about this on 23-24 July on wine-devel. It reached no conclusion, though, and I didn't try the various MinGW libraries recommended there. The abundance of MinGW packages always confused me, and at the moment I don't even know where I got mine from. But it can't compile the dsound tests, that's for sure. Comments welcome. -- Feri.

2 1

Re: patch: shell32.dll - SHELL_ArgifyW expands env-vars
by Steven Edwards 08 Aug '04

08 Aug '04

Hi Jens, --- Jens Collin <jens.collin(a)lakhei.com> wrote: > * lookup of envoronment-vars in SHELL_ArgifyW in shell32.dll added. > (Such as %SystemRoot%). Do you think you could write some test cases for the shellexecute functions using the wine regression tests? I would like to try and merge the rest of shell32 in to ReactOS but am worried that we may overwrite fixes Martin made in the ReactOS tree. Thanks Steven __________________________________ Do you Yahoo!? Y! Messenger - Communicate in real time. Download now. http://messenger.yahoo.com

2 1

Wine's OLE/COM doesn't work, and I can no longer use native COM
by David D. Hagood 08 Aug '04

08 Aug '04

One of the few Windows programs I use is Delorme's MapNGo (versions 4 and 6). Under older versions of Wine wherein I could use the native Windows OLE/COM implementation it worked fairly well, but with the new Wine it does not. The symptoms are that the program cannot create the initial document object - this ususally is an indication that the DLLS implementing the COM classes for the MapNGo object are not registered correctly with the system. However, I have taken a system running an older version of Wine that could successfully run Mng6 and upgraded it to the latest CVS of Wine, and it broke the app. Not being a wiz at COM, I am not sure where to go from here, other than to report the results of tracing the run: WINDEBUG=+ole,+com wine ./Mng6 fixme:ole:CoRegisterMessageFilter stub err:msg:DispatchMessageW BeginPaint not called on WM_PAINT for hwnd 0x1003a! [wowbaggr@surfer AAAMNG6]$ [wowbaggr@surfer AAAMNG6]$ WINDEBUG=+ole,+com wine ./Mng6.mdb wine: cannot determine executable type for L"D:\\AAAMNG6\\Mng6.mdb" [wowbaggr@surfer AAAMNG6]$ WINDEBUG=+ole,+com wine ./mng mng6.cnt mng6.exe mng6.hlp mngfeat.hlp [wowbaggr@surfer AAAMNG6]$ WINDEBUG=+ole,+com wine ./mng6.exe fixme:ole:CoRegisterMessageFilter stub err:msg:DispatchMessageW BeginPaint not called on WM_PAINT for hwnd 0x1003a! [wowbaggr@surfer AAAMNG6]$ [wowbaggr@surfer AAAMNG6]$ WINDEBUG=+all wine ./mng6.exe fixme:ole:CoRegisterMessageFilter stub err:msg:DispatchMessageW BeginPaint not called on WM_PAINT for hwnd 0x1003a! [wowbaggr@surfer AAAMNG6]$ [wowbaggr@surfer AAAMNG6]$ WINEDEBUG=+ole,+com wine ./mng6.exe trace:ole:DllMain 0x40c00000 0x1 0x1 trace:ole:DllMain (0x40e30000,1,0x1) trace:ole:CoInitializeEx ((nil), 2) trace:ole:CoInitializeEx () - Initializing the COM libraries trace:ole:RunningObjectTableImpl_Initialize () trace:ole:OleInitialize ((nil)) trace:ole:CoInitializeEx ((nil), 2) trace:ole:OleInitialize () - Initializing the OLE libraries trace:ole:OLEClipbrd_Initialize () fixme:ole:CoRegisterMessageFilter stub trace:ole:WINE_StringFromCLSID 0x49d964->{F4B4E540-7F32-11CE-AC56-0000C0496D91} trace:ole:WINE_StringFromCLSID 0x487530->{D97A6266-C342-11D2-A562-A313798CEB30} trace:ole:WINE_StringFromCLSID 0x4071f3bc->{D97A6266-C342-11D2-A562-A313798CEB30} trace:ole:CoGetClassObject CLSID: {d97a6266-c342-11d2-a562-a313798ceb30}, IID: {b196b28f-bab4-101a-b69c-00aa00341d07} trace:ole:COMPOBJ_DLLList_Add trace:ole:CoInitializeEx ((nil), 2) trace:ole:WINE_StringFromCLSID 0x5f8a41b8->{00025E15-0000-0000-C000-000000000046} trace:ole:CoGetClassObject CLSID: {00025e15-0000-0000-c000-000000000046}, IID: {b196b28f-bab4-101a-b69c-00aa00341d07} trace:ole:COMPOBJ_DLLList_Add trace:ole:CreateErrorInfo (0x4071f38c): stub: trace:ole:IErrorInfoImpl_QueryInterface (0x40252658)->( IID: {22f03340-547d-101b-8e65-08002b2bd119},0x4071f38c) trace:ole:ICreateErrorInfoImpl_AddRef (0x40252658) trace:ole:IErrorInfoImpl_AddRef (0x40252658)->(count=1) trace:ole:IErrorInfoImpl_QueryInterface -- Interface: (0x4071f38c)->(0x4025265c)trace:ole:IErrorInfoImpl_Release (0x40252658)->(count=2) trace:ole:ICreateErrorInfoImpl_QueryInterface (0x40252658) trace:ole:IErrorInfoImpl_QueryInterface (0x40252658)->( IID: {1cf2b120-547d-101b-8e65-08002b2bd119},0x4071f390) trace:ole:IErrorInfoImpl_AddRef (0x40252658)->(count=1) trace:ole:IErrorInfoImpl_QueryInterface -- Interface: (0x4071f390)->(0x40252658)trace:ole:ICreateErrorInfoImpl_SetGUID (0x40252658)->({00000000-0000-0000-0000-000000000000}) trace:ole:ICreateErrorInfoImpl_SetSource (0x40252658) trace:ole:ICreateErrorInfoImpl_SetDescription (0x40252658) trace:ole:ICreateErrorInfoImpl_SetHelpContext (0x40252658) trace:ole:SetErrorInfo (0, 0x40252658) trace:ole:IErrorInfoImpl_AddRef (0x40252658)->(count=2) trace:ole:IErrorInfoImpl_Release (0x40252658)->(count=3) trace:ole:ICreateErrorInfoImpl_Release (0x40252658) trace:ole:IErrorInfoImpl_Release (0x40252658)->(count=2) err:msg:DispatchMessageW BeginPaint not called on WM_PAINT for hwnd 0x1003a! (this last message usually happens when Mng tries to show an error dialog at startup.) When I've tried re-installing Mng6, I get messages from Wine about "Registering a non-oleautomation interface" - I do not know if this is significant or not. So, any pointers on where to go from here?

2 5

Re: Take monospace fonts into account in default font selectionalgorithm.
by Alexandre Julliard 07 Aug '04

07 Aug '04

Mike Hearn <mike(a)navi.cx> writes: > On Sat, 2004-08-07 at 23:16 +0900, Dmitry Timoshkov wrote: >> This can't work because instead of logical boolean results you compare >> binary flags which are different: >> >> #define FT_FACE_FLAG_FIXED_WIDTH ( 1L << 2 ) >> >> #define MONO_FONT 0x08 > > You are right. I will watch out for this in future! Here is a fixed > patch. The correct way to compare booleans in C is to invert them, i.e. instead of (a == b) use (!a == !b). You must not rely on booleans being always 0 or 1. -- Alexandre Julliard julliard(a)winehq.org

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel