On 3 September 2012 00:51, Adam Jakubek wrote:
> Hi,
>
> This patch causes wined3d to use backup swapchain DC when
> IDirect3DDevice9 is created using the desktop window.
> Windows allows to create such device as long its type is
> D3DDEVTYPE_REF or D3DDEVTYPE_NULLREF.
>
> Unpatched Wine will fail
For instance, D3DXSHAdd and D3DXSHDot accept order>D3DXSH_MAXORDER. So we must
check whether it is acceptable for other D3DXSH functions to give such an
order. If it is not acceptable, then we must know what the function returns.
For the out of bound problem, I agree that we reach an out of bou
As I understand it, you need to set up a mingw build as in
http://wiki.winehq.org/CompilingDLLsUsingMingw
Hi folks,
how does one build the native version of winetest.exe?
I looked around a bit, and didn't see any obvious instructions.
http://www.winehq.org/pipermail/wine-devel/2011-July/091144.html
touches on it, but doesn't say much.
I ask because I'm interested in tracking down why testbot
doesn't
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=21350
Your paranoid android
On 02.09.2012 22:28, Nozomi Kodama wrote:
+for (order = 0; order < 10; order++)
Is there a reason why we'd want to test til 9? D3DXSH_MAXORDER is 6, so
7 Should be enough? I know the other test do this, but technically I see
no reason for that. Specifically the if (.. order > D3DXSH_M
On 26 August 2012 18:56, André Hentschel wrote:
> It's for http://bugs.winehq.org/show_bug.cgi?id=30598
> So it has its reason
>
So assuming I don't feel like reading through various bug trackers to
figure this out, what is the specific issue this patch is supposed to
address?
On Sun, Sep 2, 2012 at 2:18 PM, Charles Davis wrote:
>...
> Er, uh, what patch?
Bah, usually Google warns me when I do that! Thanks!
Erich
On 2 September 2012 10:58, Hiroshi Miura wrote:
>
> -Set TLS1.1/1.2 disabled by Default that is
> same as Windows 7 default.
>
Aside from whether disabling TLS1.1+ is appropriate or not, or if this
is the right implementation, this patch also add %COMPAT to the
priority string, which wasn
On Sep 2, 2012, at 11:23 AM, Erich E. Hoover wrote:
> This patch adds the final feature to make the embedded help work
> properly, allowing Elster to resize the HTML Help window whenever the
> application window is resized. Without this feature the HTML Help
> window would always remain at the s
On Wed, Aug 8, 2012 at 7:27 AM, Dan Kegel wrote:
> Testing vcomp100 does work, but I shouldn't need to
> do that until there's some vcomp100-specific code.
>
> msvcr90/tests just adds a manifest, and that works.
Heh. It does add a manifest, but I don't think it works.
See http://bugs.winehq.org/
> On related note, I seriously consider dropping debug builds and replace
> them by unstripped release build or even just a separated package
> containing only debug symbols for the release build.
No one has complained about the debugging symbols in Wine Mono yet.
They are included mostly because
Hi all,
It's time for another Gecko update. I've uploaded to SourceForge [1] new
Gecko builds. These are based on Firefox 16 beta. Other than tons of
changes inherited from Firefox and usual fixes to keep it working well
for us, it brings a few visible fixes:
- Proper tag handling
- Synchronous
Hi all,
It's time for another Gecko update. I've uploaded to SourceForge [1] new
Gecko builds. These are based on Firefox 16 beta. Other than tons of
changes inherited from Firefox and usual fixes to keep it working well
for us, it brings a few visible fixes:
- Proper tag handling
- Synchronous
Hi all,
It's time for another Gecko update. I've uploaded to SourceForge [1] new
Gecko builds. These are based on Firefox 16 beta. Other than tons of
changes inherited from Firefox and usual fixes to keep it working well
for us, it brings a few visible fixes:
- Proper tag handling
- Synchronous
>> Probably this should be a win_slip().
>
> The function exists only since Windows 7/Vista (not XP) and is not yet
> in Wine (and might take a while, as my time is limited currently
> and my knowledge of this specific function same).
>
> So I think "skip" is currently the right thing ;)
I think a
On Sun, Sep 02, 2012 at 11:40:52PM +0900, Dmitry Timoshkov wrote:
> Marcus Meissner wrote:
>
> > +if (!pInitializeConditionVariable) {
> > +skip("no condition variable support.\n");
> > +return;
> > +}
>
> Probably this should be a win_slip().
The function exists only si
Marcus Meissner wrote:
> +if (!pInitializeConditionVariable) {
> +skip("no condition variable support.\n");
> +return;
> +}
Probably this should be a win_slip().
> +/* fprintf(stderr,"produced %d, c1 %d, c2 %d\n", totalproduced, cnt1,
> cnt2); */
> +
> +/* The s
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=21332
Your paranoid android
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=21331
Your paranoid android
20 matches
Mail list logo
