September 2007 - Wine-Devel

Re: WineD3D: PBO support 2/2 (attempt 2)
by Alexandre Julliard Sept. 12, 2007

Sept. 12, 2007

"Roderick Colenbrander" <thunderbird2k(a)gmx.net> writes: > This is an updated version of the patch. In the previous one I was > making a glBindBuffer call in a place without checking if PBOs were > around. Further the place didn't need the call anymore. This breaks the tests for me: ../../../tools/runtest -q -P wine -M d3d9.dll -T ../../.. -p d3d9_test.exe.so visual.c && touch visual.ok visual.c:2043: Test failed: quad 1 has color 0000ffff, expected 0x00FFFF00 visual.c:2045: Test failed: quad 2 has color 0000ffff, expected 0x0000000 visual.c:2047: Test failed: quad 3 has color 0000ffff, expected 0x0000FF00 make[2]: *** [visual.ok] Error 3 -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [bugzilla] replace generic severity descriptions with wine specific ones
by Jeremy Newman Sept. 11, 2007

Sept. 11, 2007

Is this the final version of this patch? Or shall I wait for an updated one from you? On Tue, 2007-09-11 at 11:31 -0700, Lei Zhang wrote: > Hi, > > This is for bug 9110. Hopefully bug reporters will stop marking their > bugs as critical and then get upset when we set it to normal.

1 0

Re: wordpad: #1 Store bar states in the registry
by Alexandre Julliard Sept. 11, 2007

Sept. 11, 2007

Alexander Nicolaysen Sørnes <alex(a)thehandofagony.com> writes: > wordpad: #1 Store bar states in the registry This doesn't work well when resizing the window, the toolbars get overwritten by the edit area. -- Alexandre Julliard julliard(a)winehq.org

2 7

Re: A fix for a problem with older games
by Stefan Dösinger Sept. 11, 2007

Sept. 11, 2007

Am Sonntag, 9. September 2007 17:10:39 schrieb Martin: That patch is not correct Are you sure that this patch really causes a problem? If you are running the game in winedbg and get an exception there it is a symptom of the DIB management in winex11.drv. You can just use "pass" to pass the exception up to the next handler(winex11.drv). The exception never reaches the app. If you really get a crash there then This->resource.allocatedMemory is pointing to a bad location, most likely NULL. This is a problem at some other place and should be fixed elsewhere. This read is a hack to work around a bug in the open source ati driver which caused a hard system crash if an exception occured during glDrawPixels. You can remove hack as a whole if it really causes problems, but this will cause hard crashes for a wide range of radeon drivers(xorg 6.8 and 7.0 at least). I think it is fixed in the latest version, but I am not sure, I'd have to test that. Since the hack is confined in one single function and doesn't have any side effects I decided to keep it.

1 0

Re: a ddraw patch
by Stefan Dösinger Sept. 11, 2007

Sept. 11, 2007

Am Sonntag, 9. September 2007 17:11:06 schrieb Martin: That patch will obviously break the game the dwTextureCaps modification was added originally... Can you check which cap that game needs that is removed in those lines?

1 0

Re: [bugzilla] replace generic severity descriptions with wine specific ones
by James Hawkins Sept. 11, 2007

Sept. 11, 2007

On 9/11/07, Lei Zhang <thestig(a)google.com> wrote: > Hi, > > This is for bug 9110. Hopefully bug reporters will stop marking their > bugs as critical and then get upset when we set it to normal. > <th>Blocker</th> - <td>Blocks development and/or testing work</td> + <td>When Wine won't start at all for any application, and there's no work + around</td> I think you've made this too specific, especially for Blocker. For example, in the new description you've left out compile errors, which is a big part of what blocker represents. The original description is fine for blocker. <th>Major</th> - <td>major loss of function</td> + <td>For a problem that is affecting most applications you run in Wine</td> + </tr> Why not something like, major loss of functionality for a wide range of applications instead of totally rewriting the definition. -- James Hawkins

3 3

Re: [bugzilla] replace generic severity descriptions with wine specific ones
by Jesse Allen Sept. 11, 2007

Sept. 11, 2007

On 9/11/07, Lei Zhang <thestig(a)google.com> wrote: > Hi, > > This is for bug 9110. Hopefully bug reporters will stop marking their > bugs as critical and then get upset when we set it to normal. > > > > > How about for minor you still keep "where an easy workaround is present". That differentiates it from normal. Jesse

1 0

Fifa 07 - wined3d regression
by Jan de Mooij Sept. 11, 2007

Sept. 11, 2007

Hi, Fifa 07 used to work fine with Wine, but around version 0.9.40-0.9.41 the game hangs when I start a new match. The text "Loading..." is displayed, but there is no progressbar because one thread terminates. I attached the results of winedbg (backtrace and some messages before the crash). This is the result of git bisect: 9ba3f389f665aae45b6a8a6861f9621b020e5c25 is first bad commit commit 9ba3f389f665aae45b6a8a6861f9621b020e5c25 Author: Stefan Dösinger <stefandoesinger(a)gmx.at> Date: Sun Jul 8 23:33:48 2007 +0200 wined3d: Initialize surfaces at creation. This patch removes a check of "GL_SUPPORT(APPLE_CLIENT_STORAGE)". If I put that check in again, the game works like before. The if-condition evaluates to True now, so it allocates the memory. But it segfaults there I think. Please let me know if you need more information. Thanks in advance! Jan de Mooij

2 2

AppDB entries
by speedator＠gmx.de Sept. 11, 2007

Sept. 11, 2007

Hi, sometimes app-entries (like Acrobat Reader) are for series of applications and versions for the single applications. Sometimes there are app-entries(like Age of Empires) for single applications in a series and version-entries for patches, betas, demos etc.. And sometimes it is a mixture. What about making this more clear? Do we need entries for the whole series? I think it is important for overview. So what about a new structure like "application / version / derived from version(subversion)"? Julian

3 2

lostwages CVS moved into GIT
by Jeremy Newman Sept. 11, 2007

Sept. 11, 2007

We have switched our website sources (previously known as lostwages), over to git. >From this point on I would prefer if all patches came from the git tree. Refer to the git documentation on the website and wiki on how to prepare patches with git. The git module is called simply "website".

1 0