August 2008 - Wine-devel - list.winehq.org

Re: [9/9] WineD3D: Advertise D3DFMT_A16B16G16R16 support
by Alexandre Julliard 04 Aug '08

04 Aug '08

Stefan Dösinger <stefan(a)codeweavers.com> writes: > I don't see a reason not to do this It doesn't work here: ../../../tools/runtest -q -P wine -M d3d9.dll -T ../../.. -p d3d9_test.exe.so visual.c && touch visual.ok visual.c:8469: Tests skipped: D3DFMT_G16R16F textures not supported visual.c:8469: Tests skipped: D3DFMT_G32R32F textures not supported visual.c:3155: Test failed: quad 1 has color 00000000, expected 0x00FFFF00 visual.c:3159: Test failed: quad 3 has color 00000000, expected 0x0000FF00 visual.c:3242: Test failed: quad 1 has color 00000000, expected 0x00FF0000 visual.c:3249: Test failed: quad 4 has color 00000000, expected 0x0033cc00 visual.c:7453: Tests skipped: Card has unconditional pow2 support, skipping conditional NP2 tests visual.c:8330: Tests skipped: Only 1 simultaneous render target supported, skipping MRT test make: *** [visual.ok] Error 4 -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [1/2] mlang: Add implementation of fnIMLangFontLink_GetCharCodePages
by Dmitry Timoshkov 04 Aug '08

04 Aug '08

"Vitaly Perov" <vitperov(a)etersoft.ru> wrote: > @@ -1855,8 +1855,56 @@ static HRESULT WINAPI fnIMLangFontLink_GetCharCodePages( > WCHAR chSrc, > DWORD* pdwCodePages) > { > - FIXME("\n"); > - return E_NOTIMPL; > + /* codepages, supported by Windows */ > + static const unsigned int processCP[] = {1250, 1251, 1252, 1253, 1254, 1255, > + 1256, 1257, 1258, 874, 932, 936, 949, 950, 0}; It doesn't really matter what code pages Windows supports, it does matter though what code pages are valid. You need to use Win32 APIs EnumSystemCodePages/GetCPInfo/MultiByteToWideChar instead of accessing Wine internals directly. -- Dmitry.

2 2

Re: [2/2] wined3d: Use CTXUSAGE_RESOURCELOAD for ActivateContext() in color_fill_fbo()
by Alexander Dorofeyev 04 Aug '08

04 Aug '08

H. Verbeet wrote: > + IWineD3DDeviceImpl_MarkStateDirty(This, STATE_RENDER(WINED3DRS_SCISSORTESTENABLE)); > + > + glDisable(GL_BLEND); > + IWineD3DDeviceImpl_MarkStateDirty(This, STATE_RENDER(WINED3DRS_ALPHABLENDENABLE)); Don't you need to also dirtify STATE_SCISSORRECT there?

2 1

Re: user32/tests: Avoid crash on win9x in win.c
by Dmitry Timoshkov 03 Aug '08

03 Aug '08

"Detlef Riekenberg" <wine.dev(a)web.de> wrote: > @@ -4765,10 +4765,14 @@ static void test_hwnd_message(void) > parent = pGetAncestor(hwnd, GA_PARENT); > ok(parent != 0, "GetAncestor(GA_PARENT) should not return 0 for message windows\n"); > ok(parent != desktop, "GetAncestor(GA_PARENT) should not return desktop for message windows\n"); > - root = pGetAncestor(hwnd, GA_ROOT); > - ok(root == hwnd, "GetAncestor(GA_ROOT) should return hwnd for message windows\n"); > + if (0) { > + /* this crash on win9x */ > + root = pGetAncestor(hwnd, GA_ROOT); > + ok(root == hwnd, "GetAncestor(GA_ROOT) should return hwnd for message windows\n"); > + } HWND_MESSAGE is not supported on win9x, so there is no point in disabling a part of the test which is not supposed to pass a all. Probably CreateWindowEx doesn't fail for some reason, so you need to find a different way to detect that. -- Dmitry.

1 0

Re: [7/9] WineD3D: Always load glFinish and glFlush from opengl32.dll
by H. Verbeet 03 Aug '08

03 Aug '08

2008/8/3 Stefan Dösinger <stefan(a)codeweavers.com>: > +/* glFinish and glFlush are always loaded from opengl32.dll, this the always have > + * __stdcall calling convention > + */ In theory WINAPI could be something else than __stdcall.

2 3

Re: xinput implementation
by chourmovs 03 Aug '08

03 Aug '08

Jeff Zaroyko wrote: > > > It's in C++ and the license looks incompatible with the LGPL. So, no > it doesn't look like it can be used. If you're looking to contribute > code, it's probably in your best interest to learn to program in C by > picking up a book such as 'The C Programming Language, second edition' > by K&R as a start, otherwise you have a large gap between not knowing > how to program in C and being able to contribute to the degree which > you've expressed interest. > > -Jeff > Hi Jeff thank you for your support I've got few notion of c, and i've never tried class programming with c++ The fact is what i found about xinput on the web use xinput msnd classes like windows.h and xinput.h How could i rewrite what is included in msdn ? How could i intercept xinput signal with c coding without any classes ? To Follow Dan instruction, my first and only aim is to write conformance test for the moment but i'm not sure i have understood what i've to do -- View this message in context: http://www.nabble.com/xinput-implementation-tp18748649p18800318.html Sent from the Wine - Devel mailing list archive at Nabble.com.

1 0

Re: msvfw32: Rename macro parameter to avoid string coincidence
by Andrew Talbot 03 Aug '08

03 Aug '08

You might want to forget this one. I guess no one is compiling Wine on a broken, pre-ANSI compiler. So the expansion of macro parameters inside string literals may well, in effect, be a non-issue. -- Andy.

1 0

(no subject)
by chourmovs vs 03 Aug '08

03 Aug '08

chourmovs(a)gmail.com

1 0

winetest sometimes shows 'crashed' and sometimes 'timeout'
by Paul Vriens 03 Aug '08

03 Aug '08

Hi, A few months ago I mentioned the fact that due to some issues with old kernel32/debugger tests there were some leftovers in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug (contains 'Debugger' which points to kernel32_test.exe) I have a feeling that on systems where this AeDebug contains normal debugger information we sometimes see 'crashed' whereas we see 'timeout' when the key still contains our own entry. Can anybody confirm this finding? What I'm actually looking for is people having a look at that registry key to see the contents. If it's indeed something containing "kernel32_test.exe" I'd like to hear about it (preferably with the tag they have used for the winetest run). One way to fix this registry key is to run 'drwtsn32 -i'. This of course restores the basic dr watson entry and not some specific debug program that was there before. -- Cheers, Paul.

1 0

re: problem loading wine test projects windows vista
by Dan Kegel 03 Aug '08

03 Aug '08

Hongbo wrote: > I really need to compile and run existing tests on window before I can write any test case for wine. The easiest way is to cross-compile them on wine and then run them on windows. To do this, say make crosstest See http://www.winehq.org/site/docs/winedev-guide/cross-compiling-tests - Dan

1 0