On Fri, 2008-01-25 at 15:06 -0600, Austin English wrote:
> What happened to the wiki? AppDB/WineHQ/Bugzilla are all fine, but
> wiki.winehq.org seems to be down.
The wiki is up. In fact, it was always up, but there was a little
problem with the DNS yesterday (I think from 1-8PM EST) that affected
"Luis C. Busquets Pérez" <[EMAIL PROTECTED]> wrote:
> diff --git a/dlls/d3dx8/d3dx8_main.c b/dlls/d3dx8/d3dx8_main.c
> index c24aedc..931e6c1 100644
> --- a/dlls/d3dx8/d3dx8_main.c
> +++ b/dlls/d3dx8/d3dx8_main.c
> @@ -32,6 +32,30 @@
> #include "wine/unicode.h"
> #include "d3dx8_private.h"
>
> +ty
Updated cross compiler rpms are available here:
http://mirzam.it.vu.nl/mingw/
I can build the full test suite from Wine 0.9.54 with these.
-Hans
> Find attached some data on d3dx8, d3dx9_xx and d3dx10_xx implementations:
> dll files by d3dx extension:
> d3dx8 1 dll files
> d3dx9_xx 13 dll files
> d3dx10_xx 4 dll files
> [...]
>
Nice work, how did you get the data?
Did you run Dependency Walker on each dll or is there a more
Hi,
I am currently looking at the user32: menu (HiliteMenuItem) test failures:
menu.c:1884: Test failed: HiliteMenuItem: Item 1 is not hilited
menu.c:1891: Test failed: HiliteMenuItem: Item 3 is not hilited
1. These are failing consistently on all platforms (see
http://test.winehq.org/data/2008
Find attached some data on d3dx8, d3dx9_xx and d3dx10_xx implementations:
dll files by d3dx extension:
d3dx8 1 dll files
d3dx9_xx 13 dll files
d3dx10_xx 4 dll files
Functions included in each d3dx:
DLL Number of functions
d3dx8 153
d3dx9_24 320
d3dx9_25
Stefan Dösinger wrote:
> Am Samstag, 26. Januar 2008 13:20:44 schrieb Henning Gerhardt:
>> Am 01/26/2008 12:50 PM schrieb Stefan Dösinger:
>>> Am Samstag, 26. Januar 2008 12:05:09 schrieb Reece Dunn:
Hi,
Looking at the ddrawmode test failures, they are because the test is
checki
Am Samstag, 26. Januar 2008 13:20:44 schrieb Henning Gerhardt:
> Am 01/26/2008 12:50 PM schrieb Stefan Dösinger:
> > Am Samstag, 26. Januar 2008 12:05:09 schrieb Reece Dunn:
> >> Hi,
> >>
> >> Looking at the ddrawmode test failures, they are because the test is
> >> checking that if the DDSD_REFRES
Am 01/26/2008 12:50 PM schrieb Stefan Dösinger:
> Am Samstag, 26. Januar 2008 12:05:09 schrieb Reece Dunn:
>> Hi,
>>
>> Looking at the ddrawmode test failures, they are because the test is
>> checking that if the DDSD_REFRESHRATE flag is set, then dwRefreshRate
>> is not 0. However, on many of the
Am Samstag, 26. Januar 2008 12:05:09 schrieb Reece Dunn:
> Hi,
>
> Looking at the ddrawmode test failures, they are because the test is
> checking that if the DDSD_REFRESHRATE flag is set, then dwRefreshRate
> is not 0. However, on many of the test platforms at
> http://test.winehq.org/data/2008011
Hi,
Looking at the ddrawmode test failures, they are because the test is
checking that if the DDSD_REFRESHRATE flag is set, then dwRefreshRate
is not 0. However, on many of the test platforms at
http://test.winehq.org/data/200801161000, they are reporting a refresh
rate of 0.
Are these bogus - du
On 25/01/2008, Dmitry Timoshkov <[EMAIL PROTECTED]> wrote:
> "Reece Dunn" <[EMAIL PROTECTED]> wrote:
>
> > The patch that I have just submitted ("gdiplus: fix the bezier arc
> > path test (on all platforms).") is a simple fix for the failing test
> > in graphicspath.c. The failure highlights gdiplu
Hi folks,
Once again you'll have to live without commits for a while, I'm off
skiing for a week...
--
Alexandre Julliard
[EMAIL PROTECTED]
13 matches
Mail list logo