- Wine-Devel - list.winehq.org

RE: Treeview +/-
by Ge van Geldorp Oct. 21, 2004

Oct. 21, 2004

> From: Jon Griffiths > > Hi, > > Fixing my own FIXME. > > Cheers, > Jon > > +wine/dlls/comctl32/treeview.c > Draw +/- correctly for large icon sizes (patch applied here: http://www.winehq.org/hypermail/wine-cvs/2004/10/0115.html) I can see that this would be an improvement for large icon sizes, but I don't think it's good for small icon sizes. See attached screenshot of regedit. Maybe the height/width at which to switch to the Rectangle drawing algorithm needs a bit of tuning? Ge van Geldorp.

1 0

scroll bars not shown
by Nicolai Kuntze Oct. 21, 2004

Oct. 21, 2004

Hi, in the application given in Bug 2302 are in some menus the scroll bars missing. I think the programm gets wrong dimensions from the size of the window. I do not have enough experience to track the bug by myself. Can someone please have a look on it? I have tried with the latest CVS checkout and comctrl32 as an native library. Yours, Nicolai ---- Diese Nachricht wurde auf Viren und andere gefaehrliche Inhalte sowie Spam untersucht.

1 0

Wine on OpenBSD
by Sascha Hanse Oct. 21, 2004

Oct. 21, 2004

Hi people, I just tried to install the recent Wine-tarball (20041019) on my OpenBSD 3.6. First I had to remove kthread.c:275: the RFTHREAD flag. Then the 'make depend && make' worked properly but the make install first fails with: /usr/bin/install -c serialui.dll.so /usr/local/lib/wine/serialui.dll.so cd `dirname setupapi/__install__` && make install gcc -g -O2 -o install install.c install.c:23: windef.h: No such file or directory install.c:24: winbase.h: No such file or directory install.c:25: winreg.h: No such file or directory install.c:26: winternl.h: No such file or directory install.c:27: winerror.h: No such file or directory install.c:28: wingdi.h: No such file or directory install.c:29: winuser.h: No such file or directory install.c:30: winnls.h: No such file or directory install.c:31: setupapi.h: No such file or directory install.c:33: wine/unicode.h: No such file or directory install.c:34: wine/debug.h: No such file or directory *** Error code 1 Stop in /home/sensei/wine-20041019/dlls/setupapi. *** Error code 1 Stop in /home/sensei/wine-20041019/dlls (line 416 of Makefile). *** Error code 1 Stop in /home/sensei/wine-20041019 (line 301 of Makefile). After that I copied all needed headerfiles into dlls/setupapi/ and finally I got these errors: [SNIP] /tmp//ccU25700.o(.text+0x18d1): In function `InstallHinfSectionW': /home/sensei/wine-20041019/dlls/setupapi/install.c:927: undefined reference to `SetupOpenInfFileW'/tmp//ccU25700.o(.text+0x18e1):/home/sensei/wine-200 41019/dlls/setupapi/install.c:930: undefined reference to `SetupInitDefaultQueueCallback'/tmp//ccU25700.o(.text+0x18f0):/home/sen sei/wine-20041019/dlls/setupapi/install.c:931: undefined reference to `SetupDefaultQueueCallbackW'/tmp//ccU25700.o(.text+0x1912):/home/sensei /wine-20041019/dlls/setupapi/install.c:934: undefined reference to `SetupTermDefaultQueueCallback'/tmp//ccU25700.o(.text+0x1918):/home/sen sei/wine-20041019/dlls/setupapi/install.c:935: undefined reference to `SetupCloseInfFile'/tmp//ccU25700.o(.text+0x193e): In function `InstallHinfSectionA':/home/sensei/wine-20041019/dlls/setupapi/install. c:950: undefined reference to `RtlCreateUnicodeStringFromAsciiz'/tmp//ccU25700.o(.text+0x195f):/home/ sensei/wine-20041019/dlls/setupapi/install.c:953: undefined reference to `RtlFreeUnicodeString'/tmp//ccU25700.o(.rodata+0x80): In function `get_field_string':/home/sensei/wine-20041019/dlls/setupapi/install.c:9 8: undefined reference to `__wine_dbch_setupapi' collect2: ld returned 1 exit status*** Error code 1 Stop in /home/sensei/wine-20041019/dlls/setupapi. *** Error code 1 Stop in /home/sensei/wine-20041019/dlls/setupapi. *** Error code 1 Stop in /home/sensei/wine-20041019/dlls (line 416 of Makefile). *** Error code 1 Stop in /home/sensei/wine-20041019 (line 301 of Makefile). Please CC me because I'm not subscribed to the list. -Sascha -- Anyone who considers arithmetical methods of producing random digits is, of course, in a state of sin. --John von Neumann (1951)

2 1

Re: Tiny optimizations of bit testing operations
by Rein Klazes Oct. 21, 2004

Oct. 21, 2004

On Wed, 20 Oct 2004 19:48:05 +0900, you wrote: > Hello, > > Changelog: > Dmitry Timoshkov <dmitry(a)codeweavers.com> > Tiny optimizations of bit testing operations. Testing with gcc 3.3.5: > - BOOL min_or_max_box = (wndPtr->dwStyle & WS_MAXIMIZEBOX) || > - (wndPtr->dwStyle & WS_MINIMIZEBOX); > + BOOL min_or_max_box = wndPtr->dwStyle & (WS_MAXIMIZEBOX | WS_MINIMIZEBOX); At moderate optimization levels (-O1) gcc compiles this to identical code. > - if((wndPtr->dwExStyle & WS_EX_LEFTSCROLLBAR) != 0) > + if (wndPtr->dwExStyle & WS_EX_LEFTSCROLLBAR) At any optimization level, gcc compiles this to identical code. > if ((wndPtr->dwStyle & WS_VSCROLL) && > - ((((wndPtr->dwExStyle & WS_EX_LEFTSCROLLBAR) != 0) && (ptClient.x <= rcClient.left + GetSystemMetrics(SM_CXVSCROLL))) || > - (((wndPtr->dwExStyle & WS_EX_LEFTSCROLLBAR) == 0) && (ptClient.x >= rcClient.right - GetSystemMetrics(SM_CXVSCROLL))))) > + (((wndPtr->dwExStyle & WS_EX_LEFTSCROLLBAR) && (ptClient.x <= rcClient.left + GetSystemMetrics(SM_CXVSCROLL))) || > + (!(wndPtr->dwExStyle & WS_EX_LEFTSCROLLBAR) && (ptClient.x >= rcClient.right - GetSystemMetrics(SM_CXVSCROLL))))) Not different then the previous example. >From the C point of view these bit logics are identical. The compiler finds that out easy. Rein. -- Rein Klazes rklazes(a)xs4all.nl

4 4

IE6: Help Engine Sputtering, Main Engine Doesn't Start, Segmentation Fault
by Dan McGhee Oct. 21, 2004

Oct. 21, 2004

At the outset I must apologize for the length of this post. This situation is intricately convoluted and, currently, I cannot interpret the information that I have collected. Right now I can only relay information that I think is relevant. I would be more than happy to generate more info, but I will need some specific direction for commands and so forth. Right now I have reached the limit of my current troubleshooting skills. My overall goal is to get Edit Studio 4, a video editing application, running in wine. It depends on the IE6 Help Engine. There are other situations with this app and that's why I don't depend on an older version of wine to run it. Right now, if I can't get IE6 to run its help engine, I can't get my app to work. Here goes on my problems with IE6. Conventions: 1013 implies wine compiled from the cvs update on October 13 and a .wine, created from that update aug implies wine version compiled from the cvs update on October 13 and a .wine from a wine version, compiled from my repository, before the 20040824 16:00:16 CDT commit Symptoms: 1. with wine from 1013 and .wine from 1013, IE6 exits with no window--this started sometime after the September snapshot 2. with wine from 1013, any version of wine that I compile, and .wine from aug, IE6 runs and Help works 3. with wine from September snapshot and .wine from 1013, IE6 creates a segmentation fault My original symptom was that I couldn't get IE6 Help to work after the September snapshot. I did a regression and identified the commit of 20040824 16:00:16 CDT as causing the problem. The commit edits this patch: http://cvs.winehq.org/patch.py?id=13475 Among other things this patch changes wine/dlls/Makefile.in wine/configure.ac wine/configure it also changes itss.dll. However, my symptoms still persist whether I use a native or builtin version of itss. I include this information because I don't know if the symptoms are separate problems or are related. I am not able to pin point the cause of Symptom 1 because I do not yet know how to update my repository to do a regression. I must wait for the archive after the October snapshot. I have reasoned, since I can get IE6 to work completely using a ~/.wine created before that August commit, that the problem lies somewhere in the "fake windows" directory. There are differences in the registry, win.ini and system.ini files, but I do not know how to diagnose them. The following excerpt, from one of the logs I created, shows that there is a completely different sequence, between the working and non-working situations, when shell32 loads for the first time: trace:loaddll:load_dll Loaded module L"c:\\windows\\system\\shell32.dll" : builtin -trace:loaddll:MODULE_FlushModrefs Unloaded module L"c:\\windows\\system\\shell32.dll" : builtin -trace:loaddll:load_dll Loaded module L"c:\\windows\\system\\shell32.dll" : builtin trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\ole32.dll" : native trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\BROWSEUI.dll" : native err:shell:ReadCabinetState Initializing shell cabinet settings trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\browselc.dll" : native -trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\RPCRT4.DLL" : native +trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\shdoclc.dll" : native +err:rebar:REBAR_WindowProc unknown msg 200b wp=00000000 lp=71180f00 +trace:loaddll:load_dll Loaded module L"c:\\windows\\system\\uxtheme.dll" : builtin +trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\RPCRT4.dll" : native +trace:loaddll:load_dll Loaded module L"c:\\windows\\system\\lz32.dll" : builtin +trace:loaddll:load_dll Loaded module L"c:\\windows\\system\\version.dll" : builtin +trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\urlmon.dll" : native trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\MSOSS.dll" : native trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\CRYPT32.dll" : native trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\OLEAUT32.dll" : native trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\WININET.dll" : native I stopped the excerpt here because this is the point at which the non-working situation exits. I have generated a log from +relay "grepped" for shell32 but do not know how to interpret it to see if I can glean any more information. This log and all the others are contained in the tarball that I have attached. It creates a directory called "wine-trouble" and contains all the information that I have generated. The README contains specifics of what I have done. As I was composing the README for inclusion here, I realized that I had not done two things. I forgot to copy shell and shell32 to my fake windows directory so that all of my tests were conducted with builtin shell and shell32. Additionally, I have not run wine compiled before the August commit with a fake windows created on October 13. I will do both of these and see if I get differenet results. I'm really interested in resolving this and would rather that I had been able to supply better information. However, my knowlege of winedbg, windows and cvs does not currently allow me to proceed further. If anyone wants me to do more, I would appreciate being pointed in the right direction, but I will need some specifics. I have found no documentation on any of the wine mailing lists or other forums to indicate that anyone else is having this problem. It could be something that I am doing. This is why I haven't yet submitted a bug report. If a bug report would be more appropriate, I will do that. Thanks, Dan

1 1

Re: [wineD3D] HW Vertex Buffer
by Raphael Oct. 21, 2004

Oct. 21, 2004

Hi again, A better patch than previous Changelog: - beta implementation of HW Vertex Buffer support (using ARB_vertex_buffer_object): locking/unlocking, creation, destruction - some wined3d headers/interface extension Todo - Bind/Unbind on rendering (use exported APIs, see IWineD3DDevice_BindVertexBuffer/IWineD3DDevice_UnbindVertexBuffer) Regards, Raphael

1 0

wine developer guide
by Eric Pouech Oct. 20, 2004

Oct. 20, 2004

While looking at the WDG (and please don't count me in about arguing whether it's WDG or WD'sG or WD'G), I came onto the Advanced Topics book after the two big ones ("Developing Wine" and "Wine Architecture") I does seem very odd to me as it right now: - it just contains "random" bits of information on some parts of wine - we don't have (yet) a uniform way to qualify something of advanced So my proposal would be to: - get rid of "Advanced Topics" book altogether, and keep only "Developing Wine" (the way we'd like development going on) and "Wine architecture" (the way it works - or it's supposed to) - move the various items from "Advanced Topics" to where they belong (see below) - maybe tag in both the "developing" and "architecture" books which parts are really advanced (change of font, specific paragraph type... pick up the visual effect you like most) The mapping that could be done would be: 14.1 Keyboard => Architecture/X11DRV DLL 14.2 Undocumented API => somewhere in the "developing" chapter 14.3 accelerators => Architecture/USER32.DLL 14.4 HW trace => somewhere in the "developing" chapter (likely in debugging) 15 Porting to new OS => somewhere in the "developing" chapter (likely in writing patches, to be renamed as "coding practice" or so) 16 Consoles => Architecture/KERNEL32.DLL 17 Address space => Architecture/6.3.4 (as advanced material) 18 Regression testing => somewhere in the "developing" chapter (in conformance tests) Likewise, the 5.1 about adding new languages could be moved into the "coding practice" part. If noone objects, I'll submit the changes. A+

1 0

Stack overflows
by Robert Lunnon Oct. 20, 2004

Oct. 20, 2004

I have been trying to make wine work properly with Solaris xlib and have been experiencing a few stack overflow exceptions eg 0009:Ret kernel32._LeaveSysLevel() retval=00000000 ret=7f86a7ba 0009:Ret user32.USER_Unlock() retval=00000000 ret=7f53f837 0009:Call ntdll.RtlEnterCriticalSection(7f579840) ret=7f549249 0009:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=7f549249 0009:Call ntdll.RtlLeaveCriticalSection(7f579840) ret=7f54926a 0009:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=7f54926a 0009:Call ntdll.RtlEnterCriticalSection(7f579840) ret=7f549249 0009:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=7f549249 err:seh:setup_exception stack overflow 0 bytes in thread 0009 eip ca096003 esp 7fc11000 stack 7fc10000-7fd10000 As I recall PE executables specify the stack size in the PE header so in the past I have used a little windows utility under wine to increase the stack allocation to the program, sometimes with mixed results. I Thought I'd post here to find out if this is known problem and what the cause is. I had presumed it was probably due to the extra call layering through xlib adding too much overhead to the stack for the app. Assuming this is the issue there were two actions I was looking at taking 1. A Wine utility to adjust the stack allocation for the executable 2. Adjust the stack allocation in wine to allow a little extra for wine over and above that requested by the app. Opinions ? Bob

1 0

Reimplementing SHGetFolder functions
by Juan Lang Oct. 20, 2004

Oct. 20, 2004

Any reason this patch wasn't applied? http://www.winehq.org/hypermail/wine-patches/2004/10/0167.html I know it's big, but I hope the test cases help demonstrate its correctness. Let me know if there's anything else I can do to help a review. Thanks, --Juan __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail

2 1

Re: Startmenu
by Robert Shearman Oct. 20, 2004

Oct. 20, 2004

Thorsten Kani wrote: > Nice Patch - looks good now! > i have changed the offsets and used SM_CXBORDER instead of SM_CXEDGE. > (According to MSDN, cxedge is used for 3D while cxborder is used for > Flat ) > This seems to fix the"draw below" issue. Visual Experience comes now > really near native. > > I noticed that SM_CXEDGE is used everywhere, regardless of Style > TBSTYLE_FLAT. > Please review my attached Patch. It seems to me that this Stylechecks > shoud be used everywhere. I don't think this is correct. If you change the return value for GetSystemMetrics(SM_CXEDGE) in wine/windows/sysmetrics.c then you can see that it does affect the spacing between border and icon (but our toolbar control doesn't exactly match the native for this). > As for String position issue, maybe i can help out with the controlspy > check. > Im interested in understanding the controls and wanted to play around > with CSpy anyway. > Suggestions ? You can download controlspy here: http://www.microsoft.com/msj/0798/controlspy.aspx It is very useful for throwing messages at the common controls, but it cannot test custom draw functionality and it is becoming dated (it is missing new functionality from comctl32 v5.80 and new controls). Rob

2 2