Hi,
I've written a test for d3d9 software cursors, but I'll need some help testing it on Windows. The behavior on Windows 10 is different from the one I remember from Windows 7. It doesn't affect the visual appearance of the cursor, but it does change how the test can verify the output.
Please give the attached test a try on Windows. I am without my test machines right now (except for one with Win10 on it), so my abilities are somewhat limited at the moment. What I am interested in is the trace() line it writes at the end. It says if the test could read back the cursor with GetDC and/or GetFrontBufferData.
Thanks, Stefan
On 15 December 2015 at 00:18, Stefan Dösinger stefandoesinger@gmail.com wrote:
Please give the attached test a try on Windows. I am without my test machines right now (except for one with Win10 on it), so my abilities are somewhat limited at the moment. What I am interested in is the trace() line it writes at the end. It says if the test could read back the cursor with GetDC and/or GetFrontBufferData.
visual.c:21579: getdc 0, get_fb_data 1
Windows 7 / AMD Radeon HD 6310
On 15 December 2015 at 14:34, Henri Verbeet hverbeet@gmail.com wrote:
visual.c:21579: getdc 0, get_fb_data 1
For what it's worth, that matches my Windows 10 VM with "Microsoft Basic Render Driver".
2015-12-15 14:41 GMT+01:00 Henri Verbeet hverbeet@gmail.com:
On 15 December 2015 at 14:34, Henri Verbeet hverbeet@gmail.com wrote:
visual.c:21579: getdc 0, get_fb_data 1
For what it's worth, that matches my Windows 10 VM with "Microsoft Basic Render Driver".
Same for me on Windows 7, Nvidia and Windows XP, AMD.