- better traces
- specific input data filling function for vertex shaders using vertex
shader declaration (and not FVF ... maybe FVF will return for fast
path with simples vertex shader declarations)
- huge vertex shader fixes:
- add and fix many vs (1.0->2.0) used opcodes in complex shaders
- improvements to programs parser: parse comments, version, ..
- add a vertex shader input filler function (parsing vertex shader
declaration): almost complete
- comments most of the traces (else flood ...)
- add more urls in comments
- indent, cleanups
SPI_ICONVERTICALSPACING and SPI_SETICONTITLEWRAP to match XP.
The SPI_SETBORDER test leaves an incorect border setting and is just
too erratic: comment it out for now.
Modified the SPI_ICONHORIZONTALSPACING, SPI_ICONVERTICALSPACING and
SPI_SETWORKAREA to not cause the icons to be reorganized.
Don't test out-of-bound values for SPI_SETKEYBOARDSPEED as behavior
differs accross Windows platforms.
On Win9x the maximum value for SPI_SETSCREENSAVETIMEOUT is 32767.
The registry keys and values stored in them for
SPI_ICONHORIZONTALSPACING and SPI_ICONVERTICALSPACING depend on the
Windows platform: ignore them.
No Windows platform seems to SPI_SETFASTTASKSWITCH: no longer test it.
The lParam of WM_SETTINGCHANGE is quite useless (even the MSDN says
so!) and varies accross Windows platforms. Ignore it.
Always check the SystemParametersInfoA return code as it fails in very
strange ways on some platforms. Skip unsupported settings.
Skip Unicode tests on platforms that don't support it.
VarBstrFromCy.
We cannot check for equality of floats or doubles because of rounding
errors. Check equality to 14 digits for doubles.
Add more precision to the expected results so that they match actual
results.
Print floating values with more precision so we know what went wrong.
Specify the locale for all variant functions that depend on it.
Added return codes for Win95. Win95 returns dates with only two digits
for the year.
Uncommented more VariantCopyInd and VariantChangeTypeEx tests.
Skip Unicode tests if the Unicode APIs are not implemented.
If the value name buffer is too small, Win9x returns the number of
characters returned as specified in the MSDN while other Windows
return the number of bytes written (including the trailing '\0').
it is not supported and simplify validity check.
Initialize the buffer format, and only from the fields we checked.
DirectSoundCreate8 fully initializes the buffer format (just in case).
Raphael Junqueira