exploring/possibly porting winelib app to support 64bit.

2013-03-31 Thread jordan
Hi list. A friend of mine and myself, have been exploring expanding a (currently, 32bit only) winelib app to support 64bit plugins in wine (64). The app is called FSThost, which is used to host win32 VST instruments and effects (.dll) as a standalone app in Gnu/linux. Webpage: http://sourceforge.n

Re: wined3d: Properly handle WS_VISIBLE and WS_EX_TOPMOST style flags on fullscreen windows.

2013-03-31 Thread Sam Edwards
On 03/29/2013 06:16 AM, Henri Verbeet wrote: I think the idea is basically ok, but I do have some comments: I think test_window_style() is a more appropriate place for the tests, and you should add them to the variants in ddraw as well. Ddraw applications in particular are very fragile in this

Problem about declarations of strcoll functions

2013-03-31 Thread Jactry Zeng
Hi folks, I tried to implement a lot of strcoll function these days, and I meet some trouble when I added the declaration into include/msvcrt/*.h. With "grep coll *.spec" in dlls/msvcrt/ we can find there was a lot of strcoll function. Some of them was implemented and some of them not: @ cdecl __

Re: Float printf precision

2013-03-31 Thread Henri Verbeet
On 31 March 2013 11:58, Stefan Dösinger wrote: > I was curious how you ended up with 8 digits. My thinking was that 32 > bit floats have a 23 bit mantissa, and one digit in the printout > encodes lb(10) bits - so you need ~6,9 digits to encode the mantissa, > which rounds up to 7. Thinking further

Float printf precision

2013-03-31 Thread Stefan Dösinger
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Henri, While overhauling the patch to hardcode local constants in the shader code I came across the TRACEs in wined3d_device_set_{vs,ps}_consts_f, which print the floats with %.8e. You changed this from %f in 979e3744f7721bef9e88fd671dfd7591c9f853

Re: wined3d: Properly handle WS_VISIBLE and WS_EX_TOPMOST style flags on fullscreen windows.

2013-03-31 Thread Henri Verbeet
On 30 March 2013 23:50, Sam Edwards wrote: > I'm a bit confused, then: Without this change, the exstyle test breaks, and > the guidelines request that every patch be atomic. They also request that all > tests be included in the same patch. I'm not sure there really is such a rule. > Off the to