- Wine-devel - list.winehq.org

Re: PATCH: dlls/comctl32/listview.c
by Andreas Mohr 14 Oct '02

14 Oct '02

On Mon, Oct 14, 2002 at 10:09:12PM +0200, Gerald Pfeifer wrote: > This is not ANSI/ISO C as far as I (and current GCC) know, so I hope > this straightforward fix is fine. > > Gerald > > ChangeLog: > Avoid GCC-specific language extension. > > Index: listview.c > =================================================================== > RCS file: /home/wine/wine/dlls/comctl32/listview.c,v > retrieving revision 1.224 > diff -u -3 -p -r1.224 listview.c > --- listview.c 11 Oct 2002 23:34:32 -0000 1.224 > +++ listview.c 14 Oct 2002 20:04:57 -0000 > @@ -4467,6 +4467,7 @@ static LRESULT LISTVIEW_GetColumnWidth(L > break; > default: > /* we don't have a 'column' in [SMALL]ICON mode */ > + ; Warum nicht einfach ein break; ? Sieht irgendwie "korrekter" aus...

1 0

Re: Fixed garbage in toolbar buttons
by Dimitrie O. Paun 14 Oct '02

14 Oct '02

On October 13, 2002 12:57 pm, Carlos wrote: > Changelog: > * Changed SRCPAINT to SRCCOPY, the first time what > it paints in hImageDC. > } else if (himl->hbmMask) { > BitBlt( hImageDC, 0, 0, cx, cy, hMaskListDC, lx, ly, SRCAND ); > - BitBlt( hImageDC, 0, 0, cx, cy, hImageListDC, lx, ly, SRCPAINT ); > + if (!bIsTransparent && himl->hbmMask) { > + BitBlt( hImageDC, 0, 0, cx, cy, hImageListDC, lx, ly, SRCPAINT ); > + } else { > + BitBlt( hImageDC, 0, 0, cx, cy, hImageListDC, lx, ly, SRCCOPY ); > + } This can not be right. It is equivalent to: PatBlt( hImageDC, 0, 0, cx, cy, PATCOPY); SelectObject(hImageDC, hOldBrush); } - } else if (himl->hbmMask) { + } else if (himl->hbmMask && !(fStyle & ILD_TRANSPARENT) && clrBk != CLR_NONE) { BitBlt( hImageDC, 0, 0, cx, cy, hMaskListDC, lx, ly, SRCAND ); BitBlt( hImageDC, 0, 0, cx, cy, hImageListDC, lx, ly, SRCPAINT ); } else { /* the image is opaque, just copy it */ TRACE(" - Image is opaque\n"); BitBlt( hImageDC, 0, 0, cx, cy, hImageListDC, lx, ly, SRCCOPY); } That is, if we have ILD_TRANSPARENT set, or clrBk == CLR_NONE, we go the SRCCOPY route, ignoring the mask, which is just the opposite of what we need to do! Alexandre, please do not apply it. -- Dimi.

3 3

Re: Changes in dlls/urlmon/umon.c
by Dimitrie O. Paun 14 Oct '02

14 Oct '02

On October 13, 2002 08:34 am, Carlos wrote: > Changelog: > * dlls/urlmon/umon.c > Changed some calls from W to A type. Please don't do that. Better implement the W functions in wininet. -- Dimi.

1 0

Re: alsa driver configuration
by Sylvain Petreolle 14 Oct '02

14 Oct '02

Set "Drivers=winealsa.drv" at section [WinMM]. Documentation is outdated about this. Developers : Whats's needeed to edit sgml files ? --- "Gabriel A. Arcos A." <gabrielarcos(a)cantv.net> a écrit : > Hi all !! I have intalled wine-20021007 and I want to use the alsa > driver on it. I have search all the documentation but I have not > found > any info. there are something to change in the ~/.wine/conf file? I'm > trying to play Counter Strike but I can't ( I have installed > propertly > the opengl stuff in compilation time of wine). > > thanks in advance. Gabriel Arcos. > > > > _______________________________________________ > wine-users mailing list > wine-users(a)winehq.com > http://www.winehq.com/mailman/listinfo/wine-users ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

3 3

Re: Fix disabled toolbar button actions
by Duane Clark 13 Oct '02

13 Oct '02

Carlos wrote: > Hello, > > Testing 12zip.exe, found that you can click in a > toolbar button what is disabled, and it shows a window. > The next patch fixes the problem, please if someone > is working in the toolbar code, check if it is a correct fix. > > Changelog: > * Fix disabled toolbar button actions. On one of my apps, fpga_editor, this completely breaks the main toolbar. The active buttons no longer work at all. Oddly enough, this app has a popup window with it's own toolbar. The buttons on this window have always appeared to be disabled, even though only some of them should be. But despite their appearance, the buttons work correctly, both before and after this patch.

1 0

Compilation errors
by Shachar Shemesh 13 Oct '02

13 Oct '02

make[2]: Entering directory `/home/sun/sources/wine/wine/dlls/d3d8' ../../tools/makedep -I. -I. -I../../include -I../../include -I/usr/X11R6/include -C. basetexture.c cubetexture.c d3d8_main.c device.c directx.c indexbuffer.c resource.c surface.c swapchain.c texture.c vertexbuffer.c volume.c volumetexture.c math.h: No such file or directory math.h was first included from device.c:26 make[2]: *** [depend] Error 1 make[2]: Leaving directory `/home/sun/sources/wine/wine/dlls/d3d8' make[1]: *** [d3d8/__depend__] Error 2 make[1]: Leaving directory `/home/sun/sources/wine/wine/dlls' make: *** [dlls/__depend__] Error 2 The strange thing is that /usr/include/math.h exists, and seems ok. Then again, it does not appear to be in the include path provided for the command. Explanations? Shachar

5 5

Changes in Bitmap behaviour
by Uwe Bonnes 13 Oct '02

13 Oct '02

Hallo, Xilinx webpack 4.2 running with native Common Controls shows an artefact in the display of bitmaps associated with the listview widget. This behaviour changed with http://cvs.winehq.com/patch.py?id=5720 by Michael Stefaniuc <mstefani(a)redhat.de>, but still is not right. Appended I have jpegs of the error. The first file (comctl32-builtin.jpeg) shows the behaviour with builtin commctl32, which looks good. The second file (comctl32-native-prepatch.jpeg) shows the behaviour with todays cvs, Michael's patch reversed and native comctl32/commctrl (NT4). We get a discontinous black background of the bitmap The last file (comctl32-native-prepatch.jpeg) is with native comctl32/commctrl (NT4) and todays unmodified cvs version. No we have a all black background. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

4 9

OpenGL textures are wrong under HalfLife
by David D. Hagood 13 Oct '02

13 Oct '02

My old motherboard died, and so I upgraded from a single P3 to a dual P3 system. I went to run HalfLife, which had been running beautifully under Wine, and now all the wall textures are screwed up. There is nothing of the proper textures in them - it's not like the colors are screwed up, more like the actual data is screwed up. However, it IS consistent from run to run - the same patterns on the same vertexes each time. The various "humans" in the level are fine - it is just the environment that is screwed. This is running the OpenGL setting in HL - I thought I'd try the DirectX setting, but all I get there is "This is not supported by your card". Now, I have upgraded XFree to the latest CVS pull, I rebuilt my kernel, and upgraded Wine, so it COULD be any of the above. However, I pulled an older version of Wine from another machine with the same results. Native GL programs like Q3A, RTCW, and UT all look fine, so the native GL layer is running well. Could this be an artifact of SMP? Or is there something that Wine does differently in accessing the GL libraries from a native app that would explain this?

1 0

Re: wine/dlls/avifil32: implemented many functions
by Dmitry Timoshkov 13 Oct '02

13 Oct '02

"Michael GЭnnewig" <MichaelGuennewig(a)gmx.de> wrote: > + LPWSTR szExt = strrchrW(szFile, L'.'); > +#define SLASH(w) ((w) == L'/' || (w) == L'\\') As were discussed many times using L prefix in order to create unicode chars/strings is wrong due to difference in size of unicode characters between windows and unix (2 vs. 4). We forced to create unicode strings explicitly: static const WCHAR fooW[] = { 'f','o','o',0 }; static const WCHAR dotW[] = { '.',0 }; static const WCHAR slashW[] = { '/',0 }; static const WCHAR bkslashW[] = { '\\',0 }; That's somewhat ugly and awkward, but it's really needed for portability. -- Dmitry.

4 5

help! latest cvs build of wine crashes every time
by Graham Stoney 13 Oct '02

13 Oct '02

Hi winers, I've built the latest cvs version of wine on my Debian stable system, and it crashes every time I run it. Here's an example: greyham(a)fred:/tmp$ wine notepad wine: Unhandled exception, starting debugger... wine: Unhandled exception, starting debugger... wine: Unhandled exception, starting debugger... (messages continue indefinitely; the debugger never gets started) It appears to be dying in X11DRV_CreateDC at the call to wine_tsx11_lock; but I suspect this is due to a stack frame corruption. Here's a gdb backtrace at the point of failure: 121 wine_tsx11_lock(); (gdb) where #0 X11DRV_CreateDC (dc=0x40393e48, pdev=0x40393e5c, driver=0x406c2c20 "DISPLAY", device=0x0, output=0x0, initData=0x0) at ../../graphics/x11drv/init.c:121 #1 0x40a72ff9 in CreateDCA (driver=0x409e19a0 "DISPLAY", device=0x0, output=0x0, initData=0x0) at ../../objects/dc.c:586 #2 0x409a622b in SYSMETRICS_Init () at ../../windows/sysmetrics.c:119 #3 0x409cf5aa in process_attach () at user_main.c:229 #4 0x409cf725 in UserClientDllInitialize (inst=1083441152, reason=1, reserved=0x1) at user_main.c:327 #5 0x40088e9f in PE_InitDLL (module=1083441152, type=1, lpReserved=0x1) at ../../loader/pe_image.c:628 #6 0x40085a6b in MODULE_InitDLL (wm=0x403718e8, type=1, lpReserved=0x1) at ../../loader/module.c:157 #7 0x40085b89 in MODULE_DllProcessAttach (wm=0x403718e8, lpReserved=0x1) at ../../loader/module.c:228 #8 0x40085b65 in MODULE_DllProcessAttach (wm=0x40371518, lpReserved=0x1) at ../../loader/module.c:223 #9 0x40085b65 in MODULE_DllProcessAttach (wm=0x40371288, lpReserved=0x1) at ../../loader/module.c:223 #10 0x40085b65 in MODULE_DllProcessAttach (wm=0x40370ff8, lpReserved=0x1) at ../../loader/module.c:223 #11 0x40085b65 in MODULE_DllProcessAttach (wm=0x0, lpReserved=0x1) at ../../loader/module.c:223 #12 0x400bd088 in start_process () at ../../scheduler/process.c:540 #13 0x400c128d in call_on_thread_stack (func=0x400bcef4) at ../../scheduler/sysdeps.c:112 (gdb) s Program received signal SIGSEGV, Segmentation fault. 0x53e58955 in ?? () Other apps fair as badly; always crashing on startup. I'm running XF86 version 4.2; there must be something about my system that is triggering the failure; otherwise you guys would be hitting it all the time. Any hints where I should start looking? Thanks, Graham

3 4