April 2016 - Wine-Devel - list.winehq.org

Re: [PATCH 2/6] wined3d: Implement texture DC creation on top of D3DKMTCreateDCFromMemory().

by Marvin

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 https://testbot.winehq.org/JobDetails.pl?Key=22197 Your paranoid android. === w1064 (32 bit ddraw2) === ddraw2.c:2360: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (64 bit ddraw2) === ddraw2.c:2360: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (32 bit ddraw4) === ddraw4.c:2545: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (64 bit ddraw4) === ddraw4.c:2545: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (32 bit ddraw7) === ddraw7.c:2275: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (64 bit ddraw7) === ddraw7.c:2275: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (32 bit ddraw1) === ddraw1.c:2209: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}. === w1064 (64 bit ddraw1) === ddraw1.c:2209: Test failed: Expected {0, 0, 512, 384}, got {0, 0, 1024, 768}.

April 14, 2016

Re: compobj.dll16: Fix implementation of StringFromGUID2.

by Nikolay Sivov

On 14.04.2016 19:44, Sebastian Lackner wrote: > -INT WINAPI StringFromGUID216(REFGUID id, LPOLESTR str, INT cmax) > +INT WINAPI StringFromGUID216(REFGUID id, LPOLESTR16 str, INT cmax) It also should use INT16, with spec file fixed accordingly.

April 14, 2016

Re: Fullscreen upscaling

by Henri Verbeet

On 14 April 2016 at 19:11, David Guillen Fandos <david(a)davidgf.net> wrote: > Looks like it didn't get much love :D > > Another possible solution (wine agnostic) would be to use an X11 server > on top of the current X11 server, since the major concern for me is > fullscreen apps. > > The original question though was something like "how many interactions > in terms of resolution does the X11 wine Drv have?" to get an idea of > how much effort would be to implement scaling. > I think ideally this kind of thing would be done by the X11 server and/or window manager/compositor. That said, if you want to do it in Wine, x11drv_surface_flush() may be a good place to start. There are going to be plenty of other things you'll need to scale as well though, like event coordinates and various queries.

April 14, 2016

Re: Fullscreen upscaling

by David Guillen Fandos

On 14/04/16 08:00, Bruno Jesus wrote: > On Thu, Apr 14, 2016 at 1:48 AM, David Guillen Fandos <david(a)davidgf.net> wrote: >> Hey there! >> >> I was looking into doing some automatic upscale for HiDPI screens (mine >> is 3200*1800). It would be some knob that allows the user to choose a x2 >> scaling for fullscreen apps and similar stuff. >> >> After reading winex11.drv I saw that it wouldn't be that hard to report >> 1/2 of the actual monitor resolution and then just upscale whatever gets >> rendered to the gdi_display (so we would have an unscaled surface and >> then blit that with a 2x scaling to the gdi_display). >> >> I guess that some other modifications would be needed though. Any >> comments on this? I think it could be useful for some people, nowadays >> that screens just got lots of pixels. > > There is a discussion about this at > https://bugs.winehq.org/show_bug.cgi?id=30056 > Looks like it didn't get much love :D Another possible solution (wine agnostic) would be to use an X11 server on top of the current X11 server, since the major concern for me is fullscreen apps. The original question though was something like "how many interactions in terms of resolution does the X11 wine Drv have?" to get an idea of how much effort would be to implement scaling. Thanks! David

April 14, 2016

Re: [v2 PATCH] dwrite/tests: A test for glyphBox* metrics

by Nikolay Sivov

On 14.04.2016 19:21, Marvin wrote: > 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 > https://testbot.winehq.org/JobDetails.pl?Key=22191 > > Your paranoid android. > > > === w864 (32 bit font) === > The test timed out > > Looks random, previous run was clean.

April 14, 2016

Re: [v2 PATCH] dwrite/tests: A test for glyphBox* metrics

by Marvin

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 https://testbot.winehq.org/JobDetails.pl?Key=22191 Your paranoid android. === w864 (32 bit font) === The test timed out

April 14, 2016

Re: [v2 PATCH 2/2] d3d10core: Support NULL RenderTargetView pointer in ClearRenderTargetView

by Marvin

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 https://testbot.winehq.org/JobDetails.pl?Key=22171 Your paranoid android. === w7u (32 bit device) === device.c:6244: Test failed: Got unexpected value 2.35098856e-038 at (0, 0). === w7pro64 (32 bit device) === device.c:6244: Test failed: Got unexpected value 2.35098856e-038 at (0, 0). === w8 (32 bit device) === device.c:6244: Test failed: Got unexpected value 2.35098856e-038 at (0, 0). === w864 (32 bit device) === device.c:6244: Test failed: Got unexpected value 2.35098856e-038 at (0, 0). === w1064 (32 bit device) === device.c:6244: Test failed: Got unexpected value 2.35098856e-038 at (0, 0). === w7pro64 (64 bit device) === device.c:6244: Test failed: Got unexpected value 2.35098856e-038 at (0, 0). === w864 (64 bit device) === device.c:6244: Test failed: Got unexpected value 2.35098856e-038 at (0, 0). === w1064 (64 bit device) === device.c:6244: Test failed: Got unexpected value 2.35098856e-038 at (0, 0).

April 14, 2016

Re: [v2 PATCH 1/2] d3d10core: Support NULL DepthStecilView pointer in ClearDepthStencilView

by Marvin

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 https://testbot.winehq.org/JobDetails.pl?Key=22170 Your paranoid android. === w7u (32 bit device) === device.c:6235: Test failed: Got unexpected value 2.35098856e-038 at (0, 0). === w7pro64 (32 bit device) === device.c:6235: Test failed: Got unexpected value 2.35098856e-038 at (0, 0). === w8 (32 bit device) === device.c:6235: Test failed: Got unexpected value 2.35098856e-038 at (0, 0). === w864 (32 bit device) === device.c:6235: Test failed: Got unexpected value 2.35098856e-038 at (0, 0). === w1064 (32 bit device) === device.c:6235: Test failed: Got unexpected value 2.35098856e-038 at (0, 0). === w7pro64 (64 bit device) === device.c:6235: Test failed: Got unexpected value 2.35098856e-038 at (0, 0). === w864 (64 bit device) === device.c:6235: Test failed: Got unexpected value 2.35098856e-038 at (0, 0). === w1064 (64 bit device) === device.c:6235: Test failed: Got unexpected value 2.35098856e-038 at (0, 0).

April 14, 2016

Re: Fullscreen upscaling

by Bruno Jesus

On Thu, Apr 14, 2016 at 1:48 AM, David Guillen Fandos <david(a)davidgf.net> wrote: > Hey there! > > I was looking into doing some automatic upscale for HiDPI screens (mine > is 3200*1800). It would be some knob that allows the user to choose a x2 > scaling for fullscreen apps and similar stuff. > > After reading winex11.drv I saw that it wouldn't be that hard to report > 1/2 of the actual monitor resolution and then just upscale whatever gets > rendered to the gdi_display (so we would have an unscaled surface and > then blit that with a 2x scaling to the gdi_display). > > I guess that some other modifications would be needed though. Any > comments on this? I think it could be useful for some people, nowadays > that screens just got lots of pixels. There is a discussion about this at https://bugs.winehq.org/show_bug.cgi?id=30056

April 14, 2016

Re: [PATCH] dwrite/tests: A test for glyphBox* metrics

by Sebastian Lackner

On 14.04.2016 06:13, Nikolay Sivov wrote: > + ok(m1->glyphBoxBottom == expected->glyphBoxBottom, "font %s: glyphBoxLeft %d, expected %d\n", wine_dbgstr_w(nameW), > + m1->glyphBoxBottom, expected->glyphBoxBottom); There is a copy&paste in the ok() message error here.

April 14, 2016