- Wine-Devel - list.winehq.org

Re: Revised Wine User Guide Introduction
by Dimitrie O. Paun Oct. 13, 2004

Oct. 13, 2004

On Sat, Oct 09, 2004 at 06:30:19PM -0700, Scott Ritchie wrote: > The version 0.9 todo list (bug 85) specifies the need for a rewritten > intro to the Wine User Guide. > > This patch is that rewritten intro. It rewords things to make Wine > easier to understand for the new user, gives it a more professional > look, and removes some outdated information. Cool. Can you please also reformat the long lines in the spirit of the original format? It makes it much more pleasant to work with... -- Dimi.

3 2

window caption buttons
by William Poetra Yoga Hadisoesen Oct. 13, 2004

Oct. 13, 2004

This is related to my last post. The buttons wine draw actually have wrong borders, like for example a normal window has this close button: ::::::::::::::::::::::::::::::00 :: 3300 :: 3300 :: #### #### 3300 :: #### #### 3300 :: ######## 3300 :: #### 3300 :: ######## 3300 :: #### #### 3300 :: #### #### 3300 :: 3300 :: 3300 ::333333333333333333333333333300 00000000000000000000000000000000 where: '::' is color ffffff '33' is color 808080 '00' is color 000000 (404040 in win2k & winxp, not sure about winme) ' ' is the background (default is c0c0c0, but d4d0c8 in win2k...) '##' is black but wine draws it as: ================================00 ==::::::::::::::::::::::::::::3300 ==:: 3300 ==:: #### #### 3300 ==:: #### #### 3300 ==:: #### #### 3300 ==:: ######## 3300 ==:: #### 3300 ==:: ######## 3300 ==:: #### #### 3300 ==:: #### #### 3300 ==:: #### #### 3300 ==:: 3300 ==33333333333333333333333333333300 0000000000000000000000000000000000 where '==' is some other color between '::' and ' ' There are two mistakes: 1. The borders aren't correct. For an active unpushed button, there should only be one "top-left edge". For a pushed button, there should be only one "bottom-right edge" (and inner/outer "top-left edge"s) 2. The 'X' should be drawn a bit more to the right and higher, and smaller. Smaller, because with the correct edges, we need to have (for an unpushed button) a spacing of 3, 2, 2, 2 pixels for the left, top, right, bottom sides respectively, between the 'X' and the edges (look at the correct example above). Higher and more to the right, because after making the 'X' smaller, it should have the correct spacing. Comments please... :) _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com

3 4

Re: PATCH: dlls/comctl32/tests/imagelist.c
by Vincent Béron Oct. 13, 2004

Oct. 13, 2004

Le mer 13/10/2004 à 04:39, Gerald Pfeifer a écrit : > Notice by my nightly builds. This function is not used at all, so > an alternative approach might be to completely yank it. It's used (in a #if 0'd) block to dump differences detected in a test, if the comparison fails. Yes it's not used currently, but I guess it is (or has been) useful in understanding why some tests failed. Maybe we can make the dumping not a compile-time choice but a runtime choice (and default on not doing it)... Vincent

1 0

Wine on Debian on sun4m
by Saulius Krasuckas Oct. 13, 2004

Oct. 13, 2004

I've decided to try compiling Wine on the Sun SPARC station 4. This machine is running Debian Woody 3.0r2. I am first time Debian installer. Is it completely wrong idea? If no, then going next: I've chose "C and C++ development" task and finished it (by tasksel), so all the related packages were installed. Now, after the run of "./configure" I run "make depend" and get into trouble: s2(a)austechia:/usr/src/wine-20040914$ make depend cd ./tools && make `basename tools/makedep` make[1]: Entering directory `/usr/src/wine-20040914/tools' gcc -c -I. -I. -I../include -I../include -DLEX_OUTPUT_ROOT="\"lex.yy\"" -Wall -pipe -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o makedep.o makedep.c In file included from makedep.c:23: ../include/wine/port.h:53: conflicting types for `mode_t' /usr/include/sys/types.h:71: previous declaration of `mode_t' ../include/wine/port.h:56: conflicting types for `off_t' /usr/include/sys/types.h:89: previous declaration of `off_t' ../include/wine/port.h:59: warning: redefinition of `pid_t' /usr/include/sys/types.h:99: warning: `pid_t' previously declared here ../include/wine/port.h:71: conflicting types for `fsblkcnt_t' /usr/include/sys/types.h:247: previous declaration of `fsblkcnt_t' ../include/wine/port.h:74: conflicting types for `fsfilcnt_t' /usr/include/sys/types.h:251: previous declaration of `fsfilcnt_t' make[1]: *** [makedep.o] Error 1 make[1]: Leaving directory `/usr/src/wine-20040914/tools' make: *** [tools/makedep] Error 2 I would like to find the primary reason of this, but am not sure about all the possible combinations of header files. Should I post the output of running ./configure?

3 5

Re: [WineHQ] s/Forums/Mailing Lists/
by Jeremy Newman Oct. 13, 2004

Oct. 13, 2004

I committed this, but when you go to the page it calls itself Forums still. My instinct was to s/Forums/Mailing Lists/g on forums.template. But I held off to see if anyone had a better idea on how to layout this page. As it stands right now, it does not make sense. On Mon, 2004-10-11 at 10:51, Dimitrie O. Paun wrote: > The latest cleanup patch seems to have reverted this change > that was discussed and implemented long ago. > > ChangeLog > s/Forums/Mailing Lists/ -- _ _ WebGeek/SysAdmin CodeWeavers -= http://www.codeweavers.com | \| |_____ __ ___ __ __ _ _ _ -= http://www.dracowulf.com | .` / -_) | | / ' \/ _` | ' \ -= mailto:jnewman(a)codeweavers.com |_|\_\___|\_/\_/|_|_|_\__,_|_||_| -= ICQ: 1711553 Yahoo: laxdragon

3 2

Re: winmm/time.c change
by Dmitry Timoshkov Oct. 13, 2004

Oct. 13, 2004

"Jeremy White" <jwhite(a)codeweavers.com> wrote: > static void TIME_TriggerCallBack(LPWINE_TIMERENTRY lpTimer) > { > - TRACE("before CallBack => lpFunc=%p wTimerID=%04X dwUser=%08lX !\n", > - lpTimer->lpFunc, lpTimer->wTimerID, lpTimer->dwUser); > + TRACE("%04lx:CallBack => lpFunc=%p wTimerID=%04X dwUser=%08lX dwTriggerTime %ld(delta %ld)\n", > + GetCurrentThreadId(), lpTimer->lpFunc, lpTimer->wTimerID, lpTimer->dwUser, > + lpTimer->dwTriggerTime, GetTickCount() - lpTimer->dwTriggerTime); That "%04lx:"/GetCurrentThreadId() shouldn't be there, that's the job of +tid debug channel. -- Dmitry.

2 1

'make check' hangs after crash in msvcrt/tests?
by Dan Kegel Oct. 12, 2004

Oct. 12, 2004

With this morning's cvs, 'make check' hangs after this point ... make[3]: Entering directory `/home/dank/winebuild/dlls/msvcrt/tests' ../../../../wine/tools/runtest -q -P wine -M msvcrt.dll -T ../../.. -p msvcrt_test.exe.so ../../../../wine/dlls/msvcrt/tests/cpp.c && touch cpp.ok fixme:msvcrt:__unDNameEx ((nil),.?AVtest1@@,0,0x40809010,0x40808fcc,(nil),2800) stub! wine: Unhandled exception (thread 005e), starting debugger... Usage: winedbg [--auto] [--gdb] cmdline Sounds like it's invoking winedbg wrong? Also, is there a way to say "I'm running these tests unattended, please don't wait for input"? - Dan -- My technical stuff: http://kegel.com My politics: see http://www.misleader.org for examples of why I'm for regime change

2 1

cvs update mystery
by Dan Kegel Oct. 12, 2004

Oct. 12, 2004

Last night I did a cvs update and built, and got a build failure dlls/amstream/amstream.c:40: parse error before "AM_Vtbl" Evidently cvs update failed to update the files in dlls/amstream, as it failed to pick up that part of this change: 2004-08-12 Alexandre Julliard <julliard(a)winehq.com> * dlls/amstream/amstream.c, dlls/amstream/main.c, dlls/avifil32/acmstream.c, dlls/avifil32/avifile.c, ... dlls/winmm/wineaudioio/audio.c, dlls/winmm/wineoss/audio.c, include/objbase.h, include/rpcproxy.h: Get rid of the non-standard ICOM_VTABLE macro. Repeated 'cvs update's didn't fix it. cd'ing into dlls/amstream and doing a cvs update directly in that directory worked, though, and got me new versions of the files in that directory. How strange. Maybe I'll stop using this newfangled cvs system and fall back on the old reliable ... uh, wait, cvs *is* the old reliable one... grr... - Dan -- My technical stuff: http://kegel.com My politics: see http://www.misleader.org for examples of why I'm for regime change

3 2

Re: Added DWebBrowserEvents and WebBrowser declaration
by Robert Shearman Oct. 12, 2004

Oct. 12, 2004

Jacek Caban wrote: > Changelog: > - Added dispinterfaces: DWebBrowserEvents and DWebBrowserEvents2 > - Added coclass: WebBrowser > - Added exdispid.h > You forgot the patch. Rob

1 0

COM inheritence
by Ann and Jason Edmeades Oct. 12, 2004

Oct. 12, 2004

Hiya, If you havent noticed, I'm trying to port the d3d8 code into wined3d and make it common for use from d3d9, and this is all COM objects. I have come across something which in theory would enable me to tidy my code simply, but I cant see how to make it work in C. Now I have a class, for example FRED who implements some common functions, and all the code for it would be in fred.c. I also have a subclass, defined called JIM, which needs to have entrypoints as per fred, plus some more, and its code resides in jim.c. Still with me...? Now previously, inside jim, I have duplicated all the common functions, but I want to avoid this and just call the one definition. My plan was to change the Vtbl to look like: IJimVtbl Jim_Vtbl = { IJimImpl_QueryInterface, IJimImpl_AddRef, IJimImpl_Release, IFredImpl_CommonFunc1, IFredImpl_CommonFunc2, : IJimImpl_UniqueFunc1 etc } I was also ensuring the variable definitions in the IJimImpl structure map precisely over the IFredImpl structure, before any unique variables are defined (I think this is a necessity for emulating subclassing in C?). Now, obviously if the common funcs need changing I can copy in the code, and change the vtbl to have a local override but at the moment I dont need to (they are mostly stubs even in the d3d8 code today). However, doing this fails to compile - It wont allow me to have a vtbl in jim.c which includes pointers to functions which are in fred.c, even if I have extern prototypes defined. Basically this is because array initialization requires constant values. However, this would seem something which is so common - ie inheritence is used all over the place. How do people handle this? I've looked through a few places in the code and cant see how this can be done. I could 'pretend' by initializing the Vtbl as I create the com object and do some LoadLibrary type dynamic addressing but I really want link time resolution not load time resolution. One solution would be to put the common routines in a header file, and #include it, but code in headers or #including modules is uaually frowned upon! I cant see any sensible way of doing this and I'd rather not do lots of code duplication if avoidable as this common class is used in about 7 other classes! Jason

2 3