December 2011 - Wine-Devel - list.winehq.org

Re: [PATCH 3/5] wined3d: Introduce a helper function for checking colors against a color key.
by Stefan Dösinger Dec. 9, 2011

Dec. 9, 2011

The patch is OK, this mail is just an answer to Henri's comment. 2011/12/8 Henri Verbeet <hverbeet(a)codeweavers.com> > +static BOOL color_in_range(const struct wined3d_color_key *color_key, > DWORD color) > +{ > + /* FIXME: Is this really how color keys are supposed to work? I think > it > + * makes more sense to compare the individual channels. */ > + return color >= color_key->color_space_low_value > + && color <= color_key->color_space_high_value; > +} > I tried to test this a while ago, but no GPU supported range color keys for blitting, and the HEL doesn't support that either. At least one of my GPUs seems to support this for YUV overlays(DDCKEYCAPS_SRCOVERLAYCLRSPACEYUV), but not RGB overlays or YUV blits. That could satisfy our curiosity, but an automated test is not possible.

1 0

Re: [2/2] user32: Make a SetFocus message test for a top level child window pass.
by Marvin Dec. 9, 2011

Dec. 9, 2011

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=15856 Your paranoid android. === W7PROX64 (64 bit msg) === Timeout === TEST64_W7SP1 (64 bit msg) === Timeout

1 0

Re: [2/2] user32: Make a SetFocus message test for a top level child window pass.
by Marvin Dec. 9, 2011

Dec. 9, 2011

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=15856 Your paranoid android. === W7PROX64 (64 bit msg) === Timeout === TEST64_W7SP1 (64 bit msg) === Timeout

1 0

Re: [1/2] user32: Add some SetFocus message tests.
by Marvin Dec. 9, 2011

Dec. 9, 2011

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=15855 Your paranoid android. === W7PROX64 (64 bit msg) === Timeout === TEST64_W7SP1 (64 bit msg) === Timeout

1 0

Re: [PATCH] Fixed a couple of warnings for 64bit targets
by Marvin Dec. 8, 2011

Dec. 8, 2011

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=15850 Your paranoid android. === WINEBUILD (build) === Make failed

1 0

how to debug wine
by winepp Dec. 8, 2011

Dec. 8, 2011

Dear sir: I downloaded the source of wine1.3.29.I want to know how does it work,so I must debug the source of wine! Can you tell me how to debug wine? Shall I need to install any other tools? Thank you very much! -- View this message in context: http://wine.1045685.n5.nabble.com/how-to-debug-wine-tp5054956p5054956.html Sent from the Wine - Devel mailing list archive at Nabble.com.

2 1

Re: usp10: add Myanmar script
by Marvin Dec. 8, 2011

Dec. 8, 2011

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=15845 Your paranoid android. === WNT4WSSP6 (32 bit usp10) === usp10.c:424: Test failed: 0:Wrong fRTL(1) usp10.c:424: Test failed: 0:Wrong fLayoutRTL(1) usp10.c:424: Test failed: 0:Wrong BidiLevel(1) usp10.c:456: Test failed: 0:Wrong fRTL(1) usp10.c:456: Test failed: 0:Wrong fLayoutRTL(1) usp10.c:456: Test failed: 0:Wrong BidiLevel(1) === W2KPROSP4 (32 bit usp10) === usp10.c:424: Test failed: 0:Wrong fRTL(1) usp10.c:424: Test failed: 0:Wrong fLayoutRTL(1) usp10.c:424: Test failed: 0:Wrong BidiLevel(1) usp10.c:456: Test failed: 0:Wrong fRTL(1) usp10.c:456: Test failed: 0:Wrong fLayoutRTL(1) usp10.c:456: Test failed: 0:Wrong BidiLevel(1)

1 0

Re: [5/6] gdi32: Substitute glyph for vertical font only. (try 2)
by Marvin Dec. 8, 2011

Dec. 8, 2011

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=15835 Your paranoid android. === W2KPROSP4 (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === WXPPROSP3 (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === W2K3R2SESP2 (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === WVISTAADM (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === W2K8SE (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === W7PRO (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === W7PROX64 (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === TEST64_W7SP1 (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === W7PROX64 (64 bit font) === font.c:3872: Test failed: FindResource error 1814 === TEST64_W7SP1 (64 bit font) === font.c:3872: Test failed: FindResource error 1814

1 0

Re: [4/6] gdi32: Add vertical fonts to font list. (try 2)
by Marvin Dec. 8, 2011

Dec. 8, 2011

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=15834 Your paranoid android. === W2KPROSP4 (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === WXPPROSP3 (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === W2K3R2SESP2 (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === WVISTAADM (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === W2K8SE (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === W7PRO (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === W7PROX64 (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === TEST64_W7SP1 (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === W7PROX64 (64 bit font) === font.c:3872: Test failed: FindResource error 1814 === TEST64_W7SP1 (64 bit font) === font.c:3872: Test failed: FindResource error 1814

1 0

Re: [3/6] gdi32: Don't remove leading '@' from face name. (try 2)
by Marvin Dec. 8, 2011

Dec. 8, 2011

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=15833 Your paranoid android. === W2KPROSP4 (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === WXPPROSP3 (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === W2K3R2SESP2 (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === WVISTAADM (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === W2K8SE (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === W7PRO (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === W7PROX64 (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === TEST64_W7SP1 (32 bit font) === font.c:3872: Test failed: FindResource error 1814 === W7PROX64 (64 bit font) === font.c:3872: Test failed: FindResource error 1814 === TEST64_W7SP1 (64 bit font) === font.c:3872: Test failed: FindResource error 1814

1 0