Yeah, that's pretty cool. I ran Lifeforce as a demo at several talks
last year, it was very convincing. (Although, frankly, running
retail DVD-ROM games on day of beta or release is an even more
convincing feat if we can pull it off.)
As somebody else pointed out, there are already appdb entries
I am thinking of going barbaric and doing WINEDEBUG=+relay,+snoop,+trace to see
how mt.exe get the wrong image size in
http://bugs.winehq.org/show_bug.cgi?id=22812
and just grep for the wrong/right sizes (0x "2b000", "176128", 0x "2b200",
"176640" ) to see where mt gets it from but none turn
Hi,
demos [1] from the demoscene are pretty demanding and freely available
stresstests, especially for everything 3D-related. The size-optimized
productions (4KB, 64KB) might also exploit some lesser known side effects
of bringing up a program. A review of running the most popular demos with
wine
Is it a legal requirement that everyone working on WINE must be a
complete arsehole, or just a project requirement?
Nye
Am 11.06.2010 20:43, schrieb Peter Davies:
> How do I get the test suite to report it success rate (as a whole) in
> a "%d tests executed (%d marked as todo, %d %s), %d skipped.\n" style.
>
> Peter
>
>
"%d tests executed" will be a huge number!
--
Best Regards, André Hentschel
On 06/11/2010 08:43 PM, Peter Davies wrote:
How do I get the test suite to report it success rate (as a whole) in
a "%d tests executed (%d marked as todo, %d %s), %d skipped.\n" style.
Peter
I guess the only way is to parse the report file yourself. The current
'parser' only calculates per
How do I get the test suite to report it success rate (as a whole) in
a "%d tests executed (%d marked as todo, %d %s), %d skipped.\n" style.
Peter
Nikolay Sivov writes:
> try2: function body moved to *Ex call, and CreateFontIndirect use it.
You should also print FIXMEs if the ignored data is used by the app.
--
Alexandre Julliard
julli...@winehq.org
On 06/11/2010 02:19 PM, GOUJON Alexandre wrote:
Le 11/06/2010 13:54, Paul Vriens a écrit :
I don't know if you have an account on the testbot so I tested it for
you:
"I submitted [to wineTestBot] my patch before sending it to wine-patches"
But many thanks for your help !!!
In that case, we hav
Hi,
Jan Hoogenraad wrote:
>Each debugging request for wine states that I should remove all winetricks.
AppDB should request something similar: minimal use of winetricks.
>However I have no way to tell, and no way to safely remove them.
IMHO one solution to your problem is to learn to use differen
On Wed, Jun 9, 2010 at 12:52 PM, velociraptor Genjix
wrote:
> Hey,
> Please look into this issue,
> http://bugs.winehq.org/show_bug.cgi?id=15118
> It seems like a fairly trivial fix which renders this application useless. A
> detailed description of the implementation needed is provided in that
>
Le 11/06/2010 13:54, Paul Vriens a écrit :
I don't know if you have an account on the testbot so I tested it for
you:
"I submitted [to wineTestBot] my patch before sending it to wine-patches"
But many thanks for your help !!!
In that case, we have to use broken(), haven't we ?
On 06/11/2010 01:20 PM, Paul Vriens wrote:
On 06/11/2010 01:13 PM, GOUJON Alexandre wrote:
Le 11/06/2010 11:58, Paul Vriens a écrit :
Those are the results from the testbot:
I know, I received the log by mail and I submitted my patch before
sending it to wine-patches but I didn't understand it
On 11 Jun 2010, at 12:17, David Hedberg wrote:
---
dlls/actxprxy/usrmarshal.c | 21 +
include/shobjidl.idl | 30 ++
2 files changed, 51 insertions(+), 0 deletions(-)
diff --git a/dlls/actxprxy/usrmarshal.c b/dlls/actxprxy/usrmarshal.c
ind
On 06/11/2010 01:13 PM, GOUJON Alexandre wrote:
Le 11/06/2010 11:58, Paul Vriens a écrit :
Those are the results from the testbot:
I know, I received the log by mail and I submitted my patch before
sending it to wine-patches but I didn't understand it as an error.
This means this new test is
Le 11/06/2010 11:58, Paul Vriens a écrit :
Those are the results from the testbot:
I know, I received the log by mail and I submitted my patch before
sending it to wine-patches but I didn't understand it as an error.
This means this new test is crashing on (that) NT4.
WNT4WSSP6.log
advapi32
On 6/11/2010 09:30, Dmitry Timoshkov wrote:
Igor Paliychuk wrote:
Updating Ukrainian translations to kernel32(ukr.nls).
file : ukrainian-kernel32-ukr-nls.patch
You forgot to mention what's wrong with current ukr.nls.
I asked Igor to update genitive months names, so it was basica
On 06/11/2010 11:42 AM, GOUJON Alexandre wrote:
Hi,
I'm wondering if my patch (62325) hasn't been reviewed yet or if you
expect a strict error-free patch.
Indeed, http://source.winehq.org/patches/data/62325.testfail shows a "No
test summary line found" for WNT4WSSP6.
If it's an issue, how to fix
Nikolay Sivov writes:
> From fb4317a2a39475c225fe04946795892c4891cd26 Mon Sep 17 00:00:00 2001
> From: Nikolay Sivov
> Date: Fri, 11 Jun 2010 01:42:06 +0400
> Subject: [PATCH] CreateFontIndirectEx implementation on top of
> CreateFontIndirect
It should of course be the other way around.
--
A
Hi,
I'm wondering if my patch (62325) hasn't been reviewed yet or if you
expect a strict error-free patch.
Indeed, http://source.winehq.org/patches/data/62325.testfail shows a "No
test summary line found" for WNT4WSSP6.
If it's an issue, how to fix it ?
Thanks
On Fri, Jun 11, 2010 at 3:34 AM, Maarten Lankhorst
wrote:
> Hello Andrew,
>
> On 11-06-10 10:18, Andrew Nguyen wrote:
>>
>> On Sun, Jun 6, 2010 at 4:03 PM, Maarten Lankhorst
>> wrote:
>>
>>>
>>> Is snd_pcm_recover the only function missing? If so change it to dlsym,
>>> and
>>> add a copy of snd
On 11 Jun 2010, at 02:42, David Hedberg wrote:
Hello everyone,
I'm having some trouble with this simple patch. Specifically, it
breaks compiling of dlls/actxprxy, producing the message:
*
/home/david/Projects/wine/git/dlls/actxprxy/actxprxy_shobjidl_p.c:
6507: undefined reference to
Hey,
Sorry I didn't mean any offence caused. It's just I saw that the new wine
release is going to fix bugs and tried to bring it to your attention.
I saw the guy Will Tipton in that bug ticket provided a detailed analysis of
the problem so it looked easy since you already would know the problem
Hello Andrew,
On 11-06-10 10:18, Andrew Nguyen wrote:
On Sun, Jun 6, 2010 at 4:03 PM, Maarten Lankhorst
wrote:
Is snd_pcm_recover the only function missing? If so change it to dlsym, and
add a copy of snd_pcm_recover to wine if it cannot find the libalsa one..
Is it a problem to es
On Sun, Jun 6, 2010 at 4:03 PM, Maarten Lankhorst
wrote:
> Is snd_pcm_recover the only function missing? If so change it to dlsym, and
> add a copy of snd_pcm_recover to wine if it cannot find the libalsa one..
Is it a problem to eschew the use of dlsym? It feels like modifying
winealsa.drv to dy
Am 11.06.2010 um 04:59 schrieb James McKenzie:
> Stefan Dösinger wrote:
>> It wasn't intended as an objection. It was mostly curiosity, because we have
>> no test in d3d9 that checks for similar behavior, and trying to actually use
>> such a shader for rendering would be somewhat odd.
>>
> It
Le 11/06/2010 03:52, James McKenzie a écrit :
How can I get OLDER information on patches from previous releases?
You should have a look at http://www.winehq.org/mailman/listinfo.
Everything is archived (patches submitted, commits and of course this
mailing list)
It's very useful when someone
27 matches
Mail list logo
