November 2004 - Wine-Devel - list.winehq.org

Scrollbars
by Nicolai Kuntze Nov. 7, 2004

Nov. 7, 2004

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

1 0

Re: D3D8
by Ann and Jason Edmeades Nov. 7, 2004

Nov. 7, 2004

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 Nov. 7, 2004

Nov. 7, 2004

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 Nov. 7, 2004

Nov. 7, 2004

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 Nov. 7, 2004

Nov. 7, 2004

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 Nov. 7, 2004

Nov. 7, 2004

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 Nov. 6, 2004

Nov. 6, 2004

"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 Nov. 6, 2004

Nov. 6, 2004

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 Nov. 6, 2004

Nov. 6, 2004

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 Nov. 6, 2004

Nov. 6, 2004

"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