Re: [3/3] d3drm: Implement IDirect3DRMMeshBuilderX_GetClassName

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=19493 Your paranoid android

Re: [2/3] d3drm: Implement IDirect3DRMLight_GetClassName

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=19492 Your paranoid android

Re: [2/2] msxml3: Support xmlns[:*] attribute nodes intelligently.

Hello again Nikolay and others, I'm back online. The first attachment is try 2 of the second patch, i.e. the one discussed in this thread. I hope it meets all of your concerns. I adjusted my plan slightly at this point: Den 12-06-2012 13:55, Ulrik Dickow skrev: > Den 12-06-2012 13:21, Nikolay

change wording of ok()-messages in winspool-tests?

Hi Francois and list, [/nitpick-mode on] I'm preparing a patch to fix typos/spelling/grammar in dlls/winspool.drv/tests/info.c, where I stumbled across repeated messages like ok( !retval, "function result wrong! False expected\n"); or ok( size == exact, "Parameter size wrong! %d expected