wine-devel

wine-devel@winehq.org

2 participants
84469 discussions

Scrollbars
by Nicolai Kuntze 08 Nov '04

08 Nov '04

Hi, I have played with my continuing bug (#2302) but I have some problems understanding the meaning of the output: fixme:win:GetWindowModuleFileNameA GetWindowModuleFileNameA(hwnd 0x40032, lpszFileName 0x40670548, cchFileNameMax 80) stub! trace:scroll:SetScrollInfo hwnd=0x10074 nBar=1 info=0x406715d4, bRedraw=1 trace:scroll:SCROLL_SetScrollInfo hwnd=0x10074 bar=1 mask=4 pos=1 trace:scroll:SCROLL_SetScrollInfo curVal=0 nPos=1 trace:scroll:SCROLL_SetScrollInfo new values: page=1 pos=0 min=0 max=0 trace:scroll:SCROLL_SetScrollInfo hide or disable trace:scroll:SCROLL_ShowScrollBar hwnd=0x10074 bar=1 horz=0, vert=0 trace:scroll:SetScrollInfo hwnd=0x10074 nBar=1 info=0x406715d4, bRedraw=1 trace:scroll:SCROLL_SetScrollInfo hwnd=0x10074 bar=1 mask=4 pos=2 trace:scroll:SCROLL_SetScrollInfo curVal=0 nPos=2 trace:scroll:SCROLL_SetScrollInfo new values: page=1 pos=0 min=0 max=0 trace:scroll:SCROLL_SetScrollInfo hide or disable trace:scroll:SCROLL_ShowScrollBar hwnd=0x10074 bar=1 horz=0, vert=0 trace:scroll:SetScrollInfo hwnd=0x10074 nBar=1 info=0x406715d4, bRedraw=1 trace:scroll:SCROLL_SetScrollInfo hwnd=0x10074 bar=1 mask=4 pos=3 trace:scroll:SCROLL_SetScrollInfo curVal=0 nPos=3 trace:scroll:SCROLL_SetScrollInfo new values: page=1 pos=0 min=0 max=0 trace:scroll:SCROLL_SetScrollInfo hide or disable trace:scroll:SCROLL_ShowScrollBar hwnd=0x10074 bar=1 horz=0, vert=0 If my blue bar in the list disappears pos Value counts how many lines under the window I am. I have added a little debug to follow the source ... From the developer I got the following snipplet: int SViewLow::ViewSetScrollY( int PPos, int PMax, int PPage) { SCROLLINFO Scroll; memset( &Scroll, 0, sizeof( Scroll)); Scroll.cbSize= sizeof( SCROLLINFO); Scroll.fMask= 0; if (PPos!=-1) Scroll.fMask|= SIF_POS; if (PMax!=-1) Scroll.fMask|= SIF_RANGE; if (PPage!=-1) Scroll.fMask|= SIF_PAGE; Scroll.nPos= PPos; Scroll.nPage= PPage; Scroll.nMax= PMax-1; return SetScrollInfo( (HWND)ViewGetHWND(), SB_VERT, &Scroll, TRUE); } Does anyone has an idea what this could be? Yours, Nicolai

2 1

Re: Re: Winetest questions
by Chris Morgan 08 Nov '04

08 Nov '04

> On Sun, Nov 07, 2004 at 02:01:13PM -0800, Dan Kegel wrote: > > 1. Why are all the archived posts to wine-test-results empty? > > See http://www.winehq.org/hypermail/wine-tests-results/2004/11 > > Every message body is empty! What's up with that? > > That's a good question. Chris, what's going on? > I suspect these are clients that have issues connecting to the net to upgrade their version of winrash since there are relatively few error reports compared to the number of test result submissions. We should really have the script ignore empty requests like this as they don't tell us anything and simply spam the mailing list every day. Chris

1 0

Re: Fix for metafile test
by Dan Kegel 08 Nov '04

08 Nov '04

jakov(a)vmlinux.org wrote: > This is from when I ran winetest.exe from the desktop: > > http://test.winehq.org/data/200411021000/2000/gdi32:metafile.txt : > > metafile.c:126:hdcDisplay 76010815 > metafile.c:154:hdcMetafile 202107C1 > metafile.c:40:hdc 76010815, emr->iType 1, emr->nSize 108, param 0022FB58 > metafile.c:40:hdc 76010815, emr->iType 82, emr->nSize 368, param 0022FB58 > metafile.c:40:hdc 76010815, emr->iType 37, emr->nSize 12, param 0022FB58 > metafile.c:40:hdc 76010815, emr->iType 84, emr->nSize 336, param 0022FB58 > metafile.c:40:hdc 76010815, emr->iType 84, emr->nSize 336, param 0022FB58 > metafile.c:40:hdc 76010815, emr->iType 37, emr->nSize 12, param 0022FB58 > metafile.c:40:hdc 76010815, emr->iType 40, emr->nSize 12, param 0022FB58 > metafile.c:40:hdc 76010815, emr->iType 14, emr->nSize 20, param 0022FB58 > metafile: 151 tests executed, 0 marked as todo, 0 failures. Here's what I get when I run 'make test' on Wine: ../../../../wine/tools/runtest -q -P wine -M gdi32.dll -T ../../.. -p gdi32_test.exe.so ../../../../wine/dlls/gdi/tests/metafile.c && touch metafile.ok metafile.c:91: Test failed: pass 0: dx[0] (1081735508) didn't match 6 metafile.c:91: Test failed: pass 0: dx[1] (1081735508) didn't match 2 metafile.c:91: Test failed: pass 0: dx[2] (1081735508) didn't match 6 metafile.c:91: Test failed: pass 0: dx[3] (1081735508) didn't match 5 metafile.c:91: Test failed: pass 0: dx[4] (1081735508) didn't match 2 metafile.c:91: Test failed: pass 0: dx[5] (1081735508) didn't match 4 metafile.c:91: Test failed: pass 0: dx[6] (1081735508) didn't match 2 metafile.c:91: Test failed: pass 0: dx[7] (1081735508) didn't match 3 metafile.c:91: Test failed: pass 0: dx[8] (1081735508) didn't match 4 metafile.c:91: Test failed: pass 0: dx[9] (1081735508) didn't match 5 metafile.c:91: Test failed: pass 0: dx[10] (1081735508) didn't match 3 metafile.c:91: Test failed: pass 0: dx[11] (1081735508) didn't match 2 metafile.c:91: Test failed: pass 0: dx[12] (1081735508) didn't match 3 metafile.c:91: Test failed: pass 0: dx[13] (1081735508) didn't match 5 metafile.c:91: Test failed: pass 0: dx[14] (1081735508) didn't match 2 metafile.c:91: Test failed: pass 0: dx[15] (1081735508) didn't match 3 metafile.c:91: Test failed: pass 0: dx[16] (1081735508) didn't match 4 metafile.c:91: Test failed: pass 0: dx[17] (1081735508) didn't match 4 metafile.c:91: Test failed: pass 0: dx[18] (1081735508) didn't match 3 metafile.c:91: Test failed: pass 0: dx[19] (1081735508) didn't match 2 metafile.c:91: Test failed: pass 0: dx[20] (1081735508) didn't match 6 metafile.c:91: Test failed: pass 0: dx[21] (1081735508) didn't match 5 metafile.c:91: Test failed: pass 0: dx[22] (1081735508) didn't match 3 metafile.c:91: Test failed: pass 0: dx[23] (1081735508) didn't match 4 metafile.c:91: Test failed: pass 0: dx[24] (1081735508) didn't match 4 metafile.c:91: Test failed: pass 0: dx[25] (1081735508) didn't match 5 metafile.c:91: Test failed: pass 0: dx[26] (1081735508) didn't match 3 metafile.c:91: Test failed: pass 0: dx[27] (1081735508) didn't match 6 metafile.c:91: Test failed: pass 0: dx[28] (1081735508) didn't match 4 metafile.c:91: Test failed: pass 0: dx[29] (1081735508) didn't match 3 metafile.c:91: Test failed: pass 0: dx[30] (1081735508) didn't match 2 metafile.c:91: Test failed: pass 0: dx[31] (1081735508) didn't match 5 metafile.c:91: Test failed: pass 0: dx[32] (1081735508) didn't match 5 metafile.c:91: Test failed: pass 0: dx[33] (1081735508) didn't match 2 metafile.c:91: Test failed: pass 0: dx[34] (1081735508) didn't match 6 metafile.c:91: Test failed: pass 0: dx[35] (1081735508) didn't match 4 metafile.c:91: Test failed: pass 0: dx[36] (1081735508) didn't match 3 metafile.c:91: Test failed: pass 0: dx[37] (1081735508) didn't match 4 metafile.c:91: Test failed: pass 0: dx[38] (1081735508) didn't match 3 metafile.c:91: Test failed: pass 0: dx[39] (1081735508) didn't match 2 metafile.c:91: Test failed: pass 0: dx[40] (1081735508) didn't match 2 metafile.c:91: Test failed: pass 0: dx[41] (1081735508) didn't match 4 metafile.c:91: Test failed: pass 0: dx[42] (1081735508) didn't match 4 make[3]: *** [metafile.ok] Error 43 Is the metafile test supposed to be broken like this under Wine? - Dan -- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html

2 2

Re: wine/ tools/wine.inf include/config.h.in dlls/ ...
by Vincent Béron 08 Nov '04

08 Nov '04

Le jeu 04/11/2004 à 16:15, Alexandre Julliard a écrit : > Log message: > Michael Jung <mjung(a)iss.tu-darmstadt.de> > Implemented a substantial part of rsaenh.dll. > > Patch: http://cvs.winehq.org/patch.py?id=14412 The committed patch doesn't compile on RH8. OpenSSL doesn't use the same name for some datatypes/functions as the version used by Michael (actually the prototype is different as well). OpenSSL 0.9.7a (as found on FC1) will use OPENSSL_ENABLE_OLD_DES_SUPPORT by default which will #define the old names to the new ones for the DES functions. RSAPrivateKey_dup is only defined in x509.h in OpenSSL 0.9.6b, not in rsa.h. But pulling in x509.h also includes md4.h, md5.h and sha.h (via evp.h), which redefine MD4_CTX (and MD5 and SHA _CTX also) with an incompatible definition if the NO_MD4, etc. are not defined. Changelog: Allow rsaenh compilation with older (0.9.6b) OpenSSL version. Remove a cast from const to not-const. Vincent

2 1

Do we need one of those on our docs?
by Shachar Shemesh 08 Nov '04

08 Nov '04

From the samba developer's guide, http://us1.samba.org/samba/devel/ > *Important:* In order to avoid any potential licensing issues we > also ask that anyone who has signed the Microsoft CIFS Royalty > Free Agreement > <http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cifs/proto…> > not submit patches to Samba, nor base patches on the referenced > specification. We ask, too, that patches submitted to Samba not > infringe on any known patents. Finally, as with all GPL work, the > submitter should ensure that submitted patches do not conflict > with any third-party copyright. > > Do we need to put in something like that too? I'm not a lawyer (but I can probably get one). My understanding is that the "protocols" Microsoft policy don't really affect us. What may affect us is the wider and wider distribution of the Windows source code (Shared Source). We should not be highly affected by trade secrets: anyone publishing a trade secret is nullifying the secretness of it, and is the one bearing the responsibility for this action. However, copyright problems may be a problem for us. If someone takes a significant amount of code from MS and submits it, we may have some backtracking to do. Shachar -- Shachar Shemesh Lingnu Open Source Consulting ltd. http://www.lingnu.com/

2 1

Re: signaling unix threads
by Dan Kegel 08 Nov '04

08 Nov '04

Mike Hearn wrote: > I quite liked Michaels idea of the RT signals. Is there some reason we > can't use them? I didn't see Michael's proposal. Can you point to it? Now, I don't pretend to understand the issues here, but reading your patch, http://www.winehq.org/hypermail/wine-patches/2004/11/att-0041/01-patch__cha… I see the comment * ... there is a race with SuspendThread(): the app * can call SuspendThread() then GetThreadContext() whilst the * target is processing SIGUSR1 but before it's been able to * override the thread context, ie the context returned would be * meaningless to the app (internals of Wine itself). I understand similar races are present in real Windows, too. e.g. http://blogs.msdn.com/cbrumme/archive/2003/08/20/51504.aspx says "[with SuspendThread,] there’s a significant risk of leaving a thread suspended at a “bad” spot. If you call SuspendThread while a thread is inside the OS heap lock, you better not try to allocate or free from that same heap. In a similar fashion, if you call SuspendThread while a thread holds the OS loader lock (e.g. while the thread is executing inside DllMain) then you better not call LoadLibrary, GetProcAddress, GetModuleHandle, or any of the other OS services that require that same lock. Even worse, if you call SuspendThread on a thread that is in the middle of exception dispatching inside the kernel, a subsequent GetThreadContext or SetThreadContext can actually produce a blend of the register state at the point of the suspension and the register state that was captured when the exception was triggered. If we attempt to modify a thread’s context (perhaps bashing the EIP – on X86 – to redirect the thread’s execution to somewhere it will synchronize with the GC or other managed suspension), our update to EIP might quietly get lost." I guess we just need to have races no worse than in Windows :-) About RT signals - I would tread carefully here. RT signals are a precious resource. The queue is not very deep, and it's *per system* on Linux IIRC. When I used RT signals for I/O, they overflowed the queue all the time -- and if any program in the system is doing that, it affects your program, since the queue is shared. - Dan -- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html

2 1

wine under cygwin
by James Hawkins 07 Nov '04

07 Nov '04

I'm trying to compile wine under cygwin, but I am getting this error: Entering directory `/home/James Hawkins/wine/dlls/dsound/tests' gcc capture.o ds3d.o ds3d8.o dsound.o dsound8.o propset.o testlist.o -o dsound_test.exe -ldsound -lole32 -luser32 -lkernel32 -ldxguid -luuid -ldxerr8 /usr/lib/w32api/libdxguid.a(dxguid.o)(.rdata+0x1f20):dxguid.c: multiple definition of `_DSPROPSETID_DirectSoundDevice' propset.o(.rdata+0x10):/home/James Hawkins/wine/dlls/dsound/tests/propset.c:62: first defined here /usr/lib/w32api/libdxguid.a(dxguid.o)(.rdata+0x1f30):dxguid.c: multiple definition of `_CLSID_DirectSoundPrivate' propset.o(.rdata+0x0):/home/James Hawkins/wine/dlls/dsound/tests/propset.c:61: first defined here collect2: ld returned 1 exit status make[3]: *** [dsound_test.exe] Error 1 make[3]: Leaving directory `/home/James Hawkins/wine/dlls/dsound/tests' make[2]: *** [tests] Error 2 make[2]: Leaving directory `/home/James Hawkins/wine/dlls/dsound' make[1]: *** [dsound] Error 2 make[1]: Leaving directory `/home/James Hawkins/wine/dlls' make: *** [dlls] Error 2 Has anyone successfully compiled wine under cygwin, or does anyone have an idea of what the problem is? -- James Hawkins

1 0

winipcfg.exe issues
by Saulius Krasuckas 07 Nov '04

07 Nov '04

[s2@katleriai antras]$ /sbin/ifconfig | grep ^[^\ ] eth0 Link encap:Ethernet HWaddr 00:50:22:80:F0:49 lo Link encap:Local Loopback ppp0 Link encap:Point-to-Point Protocol If run winipcfg with Wine, it lets me to change the adapter I want to inspect by selecting its name in combox (as usually). But if I hold the down-key pressed down for some seconds, Wine terminates the application: [s2@katleriai antras]$ wine /home/s2/cc/Program\ Files/winipcfg.exe wine client error:21: no fd received for handle 88 While the key is pressed, adapter info is being periodically refreshed. Does that means the app leaks some handle? Or is this a bug in Wine? What debug channel would you recommend to use to see more details on this?

1 0

SetupComm insize 1600 outsize 1600
by MediaHost (TM) 07 Nov '04

07 Nov '04

Hi Wine Developers, Question: I need to use a Win app on Linux and everything seams fine, except that the communication with the serialport doesn't work. Well, also here, everything seams fine to me, so I want to get your advice. The only thing I could see is the unimplemented stub for "SetupComm insize outsize". Can I set it by my own (setserial) or what's the meaning of it anyway? The output below seams to me pretty good...: fixme:comm:SetupComm insize 1600 outsize 1600 unimplemented stub trace:comm:GetCommState handle 0x54, ptr 0x778ef948 trace:comm:GetCommState OK trace:comm:GetCommState bytesize 8 baudrate 2400 fParity 0 Parity 0 stopbits 1 trace:comm:GetCommState ~IXON ~IXOFF trace:comm:GetCommState fOutxCtsFlow 0 fRtsControl 1 trace:comm:GetCommState fOutxDsrFlow 0 fDtrControl1 trace:comm:GetCommState ~CRTSCTS trace:comm:SetCommState handle 0x54, ptr 0x778ef948 trace:comm:SetCommState bytesize 8 baudrate 1200 fParity 0 Parity 0 stopbits 1 trace:comm:SetCommState ~IXON ~IXOFF trace:comm:SetCommState fOutxCtsFlow 0 fRtsControl 1 trace:comm:SetCommState fOutxDsrFlow 0 fDtrControl1 trace:comm:EscapeCommFunction handle 0x54, function=5 trace:comm:EscapeCommFunction SETDTR trace:comm:EscapeCommFunction handle 0x54, function=4 trace:comm:EscapeCommFunction CLRRTS trace:comm:SetCommTimeouts (0x54,0x778ef934) trace:comm:PurgeComm handle 0x54, flags 4 trace:comm:PurgeComm handle 0x54, flags 8 ]# cat /proc/tty/driver/serial serinfo:1.0 driver:5.05c revision:2001-07-08 0: uart:16550A port:3F8 irq:4 baud:2400 tx:11 rx:0 RTS Best Regards Signer: Eddy Nigg Company: StartCom Linux at www.startcom.org MediaHostT at www.mediahost.org Skype: startcom

2 2

Scrollbars
by Nicolai Kuntze 07 Nov '04

07 Nov '04

1 0

Re: D3D8
by Ann and Jason Edmeades 07 Nov '04

07 Nov '04

All I can say is any assistance with the d3d8/9 stuff is very gratefully accepted! If you have any questions or want help, feel free to drop me a note or post on wine-devel, and I'll try to respond. As per Lionel's note, I'm trying to move all the code into wined3d and make d3d8 and d3d9 call it, effectively making only one place to maintain so there is a lot of churn at the moment. It should settle in a couple of months (Once I get my latest patch in, things will move faster as well, once I know the way to solve certain problems). If you want suggestions as to what to work on, there's enough areas :-) - One I would say needs doing at some point is to take eg. 3dMark2002se, and get figures for it (I'd be interested if someone has a dual boot windows/linux machine to get comparisons on time), and try some profiling to work out where the time is spent and speed things up! - Apart from that, pick a game, and get the graphics right! - Or search the web for d3d8 (or 9, when it's there) demos which don't work and you have the source as well to, as you then know where to target in Jason

1 0

STL with WINE problems
by Dagan Shai 07 Nov '04

07 Nov '04

Hi, I'm trying to compile a C++ file using WINE. The file includes STL's map. I am using STLPort with WINE. I get a long list of errors starting with: /starhome/iu/wine/include/wine/msvcrt/cstdlib:97: `div' not declared /starhome/iu/wine/include/wine/msvcrt/cstdlib:102: `ldiv' not declared /starhome/iu/wine/include/wine/msvcrt/cstdlib: In function `ldiv_t std::div(long int, long int)': /starhome/iu/wine/include/wine/msvcrt/cstdlib:122: `ldiv' undeclared (first use this function) /starhome/iu/wine/include/wine/msvcrt/cstdlib:122: (Each undeclared identifier is reported only once for each function it appears in.) /starhome/iu/wine/include/wine/msvcrt/cstdlib: At global scope: /starhome/iu/wine/include/wine/msvcrt/cstdlib:138: `lldiv_t' not declared /starhome/iu/wine/include/wine/msvcrt/cstdlib:139: `_Exit' not declared ... I'm using msvcrt as the C library. I saw a previous posting with the same problem, and I've tried the various solutions suggested (toggling -mno-cygwin, using STLPort) but that did not work. Suggestions welcome. Thanks, Shai Dagan

1 0

D3D8
by Joel Konkle-Parker 07 Nov '04

07 Nov '04

In trying to get Guild Wars to work, I've come across the lack of D3D8 support in Wine. I'd like to try to help on this front, but I'm not sure who to talk to or where to start. Cedega has D3D8 support, but I'm presuming that if I contribute there, my code won't migrate back to base Wine. Can anyone lead me in the right direction here? -- Joel Konkle-Parker Webmaster [Ballsome.com] E-mail [jjk3(a)msstate.edu]

4 4

Re: Frame and Button Edges
by Dan Kegel 07 Nov '04

07 Nov '04

williampoetra(a)yahoo.com wrote: > Patch submitted to wine-cvs. Hope it gets committed :) I hope you meant wine-patches. wine-cvs is only for things that have already been committed, I think... - Dan -- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html

2 1

Countering arguments against Wine
by Dan Kegel 07 Nov '04

07 Nov '04

I've run into people several times who dislike the fact that I advocate or even work on the Wine project, because they feel that it takes focus away from working on the Linux desktop. I beg to differ, but I've never had a really snappy comeback for them. It happened again today, and this time it occurred to me I should write a page on the topic to organize my thoughts. Here it is: http://www.kegel.com/wine/why.html Comments welcome. Thanks, Dan -- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html

6 11

Re: MSIEXEC: Make installation of InstMsiA.exe possible
by Dmitry Timoshkov 06 Nov '04

06 Nov '04

"Hans Leidekker" <hans(a)it.vu.nl> wrote: > @@ -523,6 +524,11 @@ > { > InstallUILevel = INSTALLUILEVEL_BASIC|INSTALLUILEVEL_PROGRESSONLY; > } > + else if(!strcasecmp(argv[i]+2, "b+!")) Please use lstrcmpiA instead of strcasecmp. A difference between unix system locale and current ANSI code page in Wine might lead to undesired side effects. -- Dmitry.

2 1

Re: MSIEXEC: Make installation of InstMsiA.exe possible
by Tobias Burnus 06 Nov '04

06 Nov '04

Hello, Hans Leidekker wrote: > I have an InstMsiA.exe that uses two undocumented msiexec command line > parameters: /m and /D and uses an undocumented modifier (!) with the /q > parameter. Our msiexec fails when it encounters these and responds with > a usage message. For /m I found the following, don't know whether it helps. Tobias According to http://safariexamples.informit.com/0321133455/ExecutiveSoftware/Diskeeper/D… msiexec /m MIF /qn /I DKMSI INSTALLDIR="C:\MyDir" Where MIF represents the Management Information File -- 8 characters maximum.

1 0

Re: keyboard: ISO_Left_Tab
by Andreas Mohr 06 Nov '04

06 Nov '04

Hi, On Sat, Nov 06, 2004 at 07:30:20AM -0800, Walt Ogburn wrote: > + /* Special case: X turns shift-tab into ISO_Left_Tab. */ > + /* Here we change it back. */ > + if ((ret == 0) && (keysym == XK_ISO_Left_Tab)) > + { > + ret = 1; > + lpChar[0] = 0x09; > + } > + > if (ret == 0) > { > BYTE dead_char; Two comments: a) A return value of 0 probably is much more common than the XK_ISO_Left_Tab keysym, so the XK_ISO_Left_Tab check should be first to not have to check both conditions in the event that ret is 0. (the compiler might do reordering according to check probability, though, but OTOH I doubt that it knows which one is more likely) b) there's another if (ret == 0) *right below*, so why not add the XK_ISO_Left_Tab check there? Again useless waste of resources... Thanks for this patch! Andreas Mohr

2 1

Re: winuser.h : remove a fixme and "add" some things
by Dmitry Timoshkov 06 Nov '04

06 Nov '04

"Rémi Assailly" <remi.assailly(a)free.fr> wrote: > Excuse me, > I did not want to write that ULONG_PTR is 32 in Win32 _and_ Win64, but I > wanted to write that ULONG_PTR and DWORD were the same. I was wrong here > : DWORD is always 32bits, no ? Right, DWORD is a 32-bit entity in both Win32 and Win64. > So, why there are a lot of ULONG_PTR instead of DWORD if it is not to be > ported in Win64 ? That's there exactly for that purpose - to be portable to Win64. That's a variable that can potentially hold a pointer or a handle value. Win64 is not binary compatible with Win32, but is aimed to be source compatible. Read some docs about porting to Win64 for further details. -- Dmitry.

1 0

err:keyboard:X11DRV_ToUnicodeEx Please report:
by Jon Griffiths 06 Nov '04

06 Nov '04

Hi, Duly reporting: err:keyboard:X11DRV_ToUnicodeEx Please report: no char for keysym FE20 (ISO_Left_Tab) : err:keyboard:X11DRV_ToUnicodeEx (virtKey=9,scanCode=F,keycode=17,state=1) This happens when I shift-tab in any Wine app. System is mdk 10.0/wine cvs and this message has been there for several months at least (when I first noticed). I'm happy to provide more info on request if someone knows how to fix this. Cheers, Jon ===== "Don't wait for the seas to part, or messiahs to come; Don't you sit around and waste this chance..." - Live jon_p_griffiths(a)yahoo.com __________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com

2 2

Frame and Button Edges
by William Poetra Yoga H 06 Nov '04

06 Nov '04

This is about frame edges and button edges on WINE... On Windows, the default behavior is the outer left-top edge of a frame is painted with COLOR_BTNFACE and the inner left-top is colored with something white (COLOR_BTNHILIGHT maybe???). But for caption buttons and push buttons, they are reversed. In WINE, the abovementioned edges, whether for a frame or for a button, are always: 1. outer left-top is COLOR_BTNFACE 2. inner left-top is white This is probably not so noticable, but it's actually quite disturbing if you ask me... For comparison, in ReactOS (0.2.4), caption buttons' edges, and toolbar buttons' edges are drawn correctly, but those of push buttons aren't. So the problem is: how do we reproduce Windows' default behavior? I have tried the styles for DrawEdge, and even made a program to try it out, but I can't seem to generate the correct edges for buttons. The source to edges.c is attached. I wanted to attach the executable but... Can I attach it? Oh, and this is off-topic: How do I use Tahoma as the default font for WINE, like in the screenshots? I think Bitstream Vera fonts look weird for Windows apps... I've searched google but found nothing that helped me... __________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com

1 1

Re: winuser.h : remove a fixme and "add" some things
by Dmitry Timoshkov 06 Nov '04

06 Nov '04

"Rémi Assailly" <remi.assailly(a)free.fr> wrote: > There were a fixme warning us that a structure were not sure ( line 1898 ). > I checked it and it seems correct. The only differences I found are : > - ULONG_PTR dwItemData instead of DWORD dwItemData which is the same > thing with win32 and also win64 ( according to what I understood ) No, they are not the same. ULONG_PTR is a 64-bit entity in Win64, but 32-bit in Win32. -- Dmitry.

1 0

Public domain source in wine
by Michael Jung 06 Nov '04

06 Nov '04

Hello, I would like to use source code from LibTomCrypt (http://libtomcrypt.org) in my implementation of rsaenh.dll (which I still hope has a remote chance of being accepted into wine ;-), in order to get rid of the OpenSSL dependencies. LibTomCrypt is in the public domain. I have two questions: 1. What is the legaly correct way to do this? As I understand it, public domain source can simply be taken as is and re-licensed under the LGPL. Is this correct? Am I allowed to remove the headers in the original file, which state that the code is public domain? How do you generally acknowledge the original author? 2. A more technical question: LibTomCrypt's original sources are highly customizable (A lot of conditional compilation and hook-functions). Since we have fairly special requirements for rsaenh, I could cut down the source code a lot. However, this would make it harder to incorporate code from a newer version of libtomcrypt, once it becomes available. Which way is preferable? Having less code or beeing easily upgradeable? Greetings, Michael

4 3

RE: [dx9-12] Major change to design
by Ann and Jason Edmeades 05 Nov '04

05 Nov '04

Ha! Spot the half written note I started a week ago when I first was trying to word a reply, which was nicely hidden off the end of my previous note! - Sorry about that :-) Jason

1 0

Re: [dx9-12] Major change to desgin
by Alexandre Julliard 05 Nov '04

05 Nov '04

"Ann and Jason Edmeades" <us(a)the-edmeades.demon.co.uk> writes: > I think this patch should keep you happy (It doesn't do any of the > IWineUserDevice stuff as the code isn't ready for it, but does the dual ref > count + adds Set/Get Stream source). Let me know if you have problems with > it. Looks much better yes, thanks. There's still something strange here: > + /* Not recording... */ > + if (oldSrc != NULL) { > + IWineD3DVertexBuffer_Release(oldSrc); > + IUnknown_Release((IUnknown *)((IWineD3DVertexBufferImpl *)oldSrc)->resource.parent); /* Released an internal reference to a VB */ > + } > + if (pStreamData != NULL) { > + IWineD3DVertexBuffer_AddRef(pStreamData); > + IUnknown_AddRef((IUnknown *)((IWineD3DVertexBufferImpl *)pStreamData)->resource.parent); /* Gained an internal reference to a VB */ > + } You shouldn't need to AddRef the parent, that's up to the object that holds the pointer (also you should do the AddRef before the Release in case old and new are the same object). -- Alexandre Julliard julliard(a)winehq.org

2 3

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