August 2007 - Wine-Devel - list.winehq.org

Re: [5/5] WineD3D: Fix fogstart == fogend with table fog

by H. Verbeet

On 21/08/07, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > Feel free to suggest a better way to increase the fogend. My way works, but it > is not the nicest way. > Does this really matter? To me, this looks like a rather ugly hack to get the DCT to shut up.

Aug. 21, 2007

Re: [2/5] WineD3D: Use 0/0/0 as normal if no normal is supplied

by H. Verbeet

I'm not sure about this one. Unless explicitly checked for, (0, 0, 0) will cause a division by zero when trying to normalize it, and I don't know for sure if GL has well defined behaviour for it.

Aug. 21, 2007

Re: How to Calling PE Dlls on linux??

by Damjan Jovanovic

On 8/21/07, trulyliu <trulyliu(a)gmail.com> wrote: > I have tried these code, It works well. Thanks a lot. > Could I use gcc/g++ instead of winegcc/wineg++ ??? > mplayer use gcc as it's complier？ What's the mystery in it? > gcc/g++ would give you the wrong ABI (eg. 4 bytes per wide char instead of 2 bytes), and the special code needed to set up the Windows memory layout and the thread extension block and structured exception handling wouldn't get executed, leading to segfaults when you call any code that tries to access them. That's assuming you can even compile and link. That's why you need winegcc/wineg++. > trulyliu(a)gmail.com Damjan

Aug. 21, 2007

Re: How to Calling PE Dlls on linux??

by Jakob Eriksson

trulyliu wrote: > > > > I have tried these code, It works well. Thanks a lot. > Could I use gcc/g++ instead of winegcc/wineg++ ??? > mplayer use gcc as it's complier？ What's the mystery in it? AFAIK mplayer uses their own old version of wine they have adapted to mplayer. regards, Jakob

Aug. 21, 2007

Re: [patch] Garbage code in text string display

by Guan Xin

On 8/20/07, James Hawkins <truiken(a)gmail.com> wrote: > It doesn't matter when you looked at the code versus when you > submitted the patch. You prove a 'bug' is necessary by writing test > cases. Also, please bottom-post in this mailing list. > > -- > James Hawkins > Acturally, I have test cases because I found where the problem resides by looking into my own Windows program's source code, which was written some years ago and has garbage code problems with WINE. Does this mail list support attachment? May I post my source code here? And maybe also a binary (.exe). However, I could only guarantee, say, 99% correctness of this patch. I thought you might want 100% confidence of its correctness when conformance test was demanded (see prev.). This can not be achieved without knowing Microsoft itself is retaining this bug. So I looked at their source code afterwards. I think I might misunderstood your meaning by "conformance test". If the test need not be thorough or guarantee 100% correctness of the patch, only my own Windows program's source code are needed. Xin

Aug. 21, 2007

Re: [Winetest RFI] What do you want out of the test suite?

by Paul Vriens

Stefan Leichter wrote: > Hello Paul, > > Am Monday 20 August 2007 11:42 schrieb Paul Vriens: >> OK, I gave it a try. >> > [snip] >> > http://www.xs4all.nl/~pvriens/200708181000_with_todo_yellow_border_and_grou… >> is the same but also shows that are are todo's for a group in the >> summary. >> > > I like the version above. > Hi Stefan, We (Feri and I) are in favor of that one as well. So I'll change the tools to handle that. The only thing we were not sure about yet is what color the left border should be as yellow was already assigned to 'mixed results'. Eventhough there's a potential 'risk' of a clash between a 'mixed result' and a todo I think we'll go with the yellow border. The reasoning is that the number of Wine reports is low anyhow thus the chances we have a clash is low as well (Wine will most likely be the only one with a yellow border). (If needed in the future, changing the color is just a minor change to the .css file). Cheers, Paul.

Aug. 21, 2007

Re: [PATCH try2 2/5] wininet: Free handle structs in WININET_Release.

by Misha Koshelev

On Mon, 2007-08-20 at 09:50 +0100, Robert Shearman wrote: > Misha Koshelev wrote: > > This is necessary so that we send the INTERNET_STATUS_HANDLE_CLOSING before, for example > > INTERNET_STATUS_CLOSE_CONNECTION gets sent from HTTP_CloseConnection in HTTP_CloseHTTPRequestHandle. > > This can be tested on native/with native wininet on wine because although we do not send > > INTERNET_STATUS_CLOSE_CONNECTION correctly when the data is finished reading on wine as native > > does, if we simply don't read all the data (or any data, changing the while TRUE's to while FALSE's > > in the InternetReadFiel_test for example in wininet/tests/http.c) then these do in fact get sent > > as a response to InternetCloseHandle like they do on wine, and INTERNET_STATUS_HANDLE_CLOSING > > always gets sent afterwards (last). > > > > It seems like it would be better to add a close_connection method to go > along with destroy, instead of leaving the handle in a half-destroyed > state. Either that, or to not use INTERNET_SendCallback to send the > callback in this case so that you don't have to have a > WININETHANDLEHEADER object still around. > Ok thanks for the comment, will think & resubmit smthng when I get a chance... busy week this week. Misha

Aug. 21, 2007

Re: winefile: Save font settings for registry

by Dmitry Timoshkov

"Ivan Sinitsin" <ivan(a)etersoft.ru> wrote: > Changelog: > this patch add opportunity to save font option to the regestry, and load font > option from regestry in the winefile program Nothing prevents you from writing and reading the whole LOGFONT structure in one go. -- Dmitry.

Aug. 21, 2007

Re: dinput compile error

by Vitaliy Margolen

Robert Reif wrote: > Lei Zhang wrote: > >> It sounds like you're missing the Linux kernel headers. >> >> On 8/20/07, Robert Reif <reif(a)earthlink.net> wrote: >> >> >>> make[2]: Entering directory `/home/wine/wine/dlls/dinput' >>> gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ >>> -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wwrite-strings >>> -Wpointer-arith -g -O2 -o joystick_linuxinput.o joystick_linuxinput.c >>> joystick_linuxinput.c:153: field `axes' has incomplete type >>> joystick_linuxinput.c:154: confused by earlier errors, bailing out >>> make[2]: *** [joystick_linuxinput.o] Error 1 >>> make[2]: Leaving directory `/home/wine/wine/dlls/dinput' >>> >>> It seems struct input_absinfo is not defined. >>> >>> >> > The headers are there or else there would have been a missing include > file error. > The needed structure is just not there in older versions of the headers. > How old are your headers? It seems that struct was added 2002-08-01 - 5 years ago!. Are you sure you have correct headers there? Oh and that was pre-2.5.x What kernel are you using again? Vitaliy.

Aug. 21, 2007

Re: How to Calling PE Dlls on linux??

by trulyliu

2007/8/20, Damjan Jovanovic <damjan.jov(a)gmail.com>: > > On 8/20/07, trulyliu <trulyliu(a)gmail.com> wrote: > > hi: > > > > I am sorry to disturb you with a question about calling PE Dll on linux. > > This is really an old question. > > I found the sameness issues in mail list. > > > > http://www.winehq.org/pipermail/wine-devel/2003-December/thread.html > > > http://www.winehq.org/pipermail/wine-devel/2005-November/thread.html#41917 > > http://www.winehq.org/pipermail/wine-users/2004-August/014685.html > > http://www.winehq.org/pipermail/wine-devel/2006-August/050619.html > > > > I have tried the ways discussed in these threads。 > > But it's not clear enough how to do this. > > So I send this mail to you for some help. > > > > I have a PE Dll named Arithmetic.dll which exports a function, > > it's prototype is: > > void sort(unsigned int*, int num) > > > > I want to call the function in my Linux App. > > You can't, it's not supported (yet), but what you want is the Wine > plugin API (http://wiki.winehq.org/WinePluginApi) > > At the moment you have 2 options: > * Make a Windows application instead of a Linux application. > * Make a winelib application which will require wine to run but can > access Linux libraries as well (with some restrictions, eg. you have > to use Windows synchronization primitives instead of the pthreads > ones). > > > I used winedump to generate a spec file > > > > winedump spec Arithmetic.dll > > > > This comand generated three files: Arithmetic_dll.h Arithmetic_main.c > and > > Arithmeticspec. > > What's the next exactly step I should do? > > What's the usage of the three files? > > And wow could I use them? > > #include <windows.h> > > int main(int argc, char **argv) > { > HANDLE h; > void (/*WINAPI?*/ *sort)(unsigned int,int); > unsigned int *nums = malloc(sizeof(unsigned int) * 4); > nums[0] = 3; > nums[1] = 2; > nums[2] = 1; > nums[3] = 0; > h = LoadLibrary("Arithmetic.dll"); > sort = GetProcAddress(h, "sort"); > sort(nums, 4); > } > > winegcc main.c -o main > ./main I have tried these code, It works well. Thanks a lot. Could I use gcc/g++ instead of winegcc/wineg++ ??? mplayer use gcc as it's complier？ What's the mystery in it? > > > I made reference to mplayer's implementation, > > It's code is a little clutter， and I don't have experience on MS D-Show. > > Could you give me some simple sample codes ?? > > MPlayer's code is GPL, so if you use it your code will be GPL too. > > > Best Regards. > > > > -- > > trulyliu(a)gmail.com > > Good luck > Damjan > > > -- trulyliu(a)gmail.com

Aug. 21, 2007