On 02/13/2010 11:49 AM, MikoĊaj Zalewski wrote:
+#define expect_eq_ws(expected, actual) \
+do { \
+ LPCWSTR value = (actual); \
+ ok(lstrcmpW((expected), value) == 0, Expected #actual to be %s ( #expected
) is %s\n, \
+ wine_dbgstr_w(expected), wine_dbgstr_w(value)); \
On 2/13/2010 15:01, Alistair Leslie-Hughes wrote:
Hi,
Changelog:
msxml4: Added support for SAXXMLReader40
Best Regards
Alistair Leslie-Hughes
Hi, Alistair.
You missed a registration part for in msxml4.
On Fri, Feb 12, 2010 at 1:55 AM, Alexandre Julliard julli...@winehq.org wrote:
Please don't create new files for every small test, this will become
unmanageable very quickly. Unless there are reasons to split them,
everything should go in a single .cmd file.
The current cmd test framework is
Hi Rico,
please have a look at the two new warnings in
http://kegel.com/wine/valgrind/logs/2010-02-12-20.25/diff-d3d10_effect.txt
http://kegel.com/wine/valgrind/logs/2010-02-12-20.25/vg-d3d10_effect.txt
Invalid free() / delete / delete[]
at notify_free (heap.c:262)
by RtlFreeHeap
On 2/13/10 4:49 PM, Dan Kegel wrote:
On Fri, Feb 12, 2010 at 1:55 AM, Alexandre Julliardjulli...@winehq.org wrote:
Please don't create new files for every small test, this will become
unmanageable very quickly. Unless there are reasons to split them,
everything should go in a single .cmd
Dan Kegel d...@kegel.com writes:
The current cmd test framework is not currently clever about
resyncing after an error, so any missing or extra line
in a test's output can cascade and cause lots of false
reports.
How about one file for each command recognized by cmd? So
there'd be
On Sat, Feb 13, 2010 at 9:02 AM, Alexandre Julliard julli...@winehq.org wrote:
the number of files must be kept small.
Is one per built-in command of wcmd too many?
- Dan
Dan Kegel d...@kegel.com writes:
On Sat, Feb 13, 2010 at 9:02 AM, Alexandre Julliard julli...@winehq.org
wrote:
the number of files must be kept small.
Is one per built-in command of wcmd too many?
At this point, yes. Once we have a thousand-line test for each command,
then it may be a
Hi folks
is it only me getting short midi-like sounds during non-interactive run of
Winetest, or is this known new bug already?
S.
On Fr, 2010-02-12 at 13:00 +0100, Alexandre Julliard wrote:
A C Hurst a.hu...@sheffield.ac.uk writes:
Fixes bug 11811 [http://bugs.winehq.org/show_bug.cgi?id=11811] and its
duplicates.
This patch sent some time back (over a year) was ignored/lost in noise.
Could someone review please?
The use of game engines has increased quite a bit
over the last couple years; there are now something
like 250 that support Windows. (And maybe five to ten
that are important commercially.)
It's tempting to consider focusing some effort on
supporting a few of them better in Wine, on the
theory
11 matches
Mail list logo
