Re: [5/5] WineD3D: Implement an ARB_fragmen_program fixed function pipeline

2008-07-27 Thread H. Verbeet
2008/7/28 Stefan Dösinger <[EMAIL PROTECTED]>: >> This enables the replacement pretty much unconditionally... do we want >> that? > I'd say so, unless we have evidence that it's a bad idea to do enable it > somewhere, and the drawback isn't fixable. > I don't mind having it on by default, but I thi

Re: [3/5] WineD3D: Optimize the fragment processing description

2008-07-27 Thread H. Verbeet
2008/7/28 Stefan Dösinger <[EMAIL PROTECTED]>: > Mostly because I've written this code before you mentioned them to me. I > think it can't hurt to ask Alexandre if bitfields are ok to use in Wine. > How's the support among compilers(older gcc versions? Non-gcc compilers like > icc and msvc?) > Afai

Device.c and set render states

2008-07-27 Thread Chris Ahrendt
While sitting on the airplane I reworked and rethought the set render states routine I sent last night and have figured out a more efficient way for it to run... Logically thinking it through 208 of the 240 states passed into this routine do nothing and have no real type checking other than to m

Re: [WideChar conversion improvements - 2/5] Implement new versions ofwctomb and wcstombs

2008-07-27 Thread Dmitry Timoshkov
"Colin Finck" <[EMAIL PROTECTED]> wrote: > -INT CDECL MSVCRT_wctomb( char *dst, MSVCRT_wchar_t ch ) > +INT CDECL MSVCRT_wctomb(char *mbchar, MSVCRT_wchar_t wchar) What's the point of the above change? > { > - return WideCharToMultiByte( CP_ACP, 0, &ch, 1, dst, 6, NULL, NULL ); > +BOOL bUse

Re: winhttp: tests/winhttp.c: Add test for WinHttpSendRequest

2008-07-27 Thread Zac Brown
Hans Leidekker wrote: > On Friday 25 July 2008 22:13:18 Zac Brown wrote: > >> +#include >> >> #include >> #include >> +#include > > You shouldn't need these. > > -Hans > Thank you, scratch this patch AJ, I'll send another.

RE: [5/5] WineD3D: Implement an ARB_fragmen_program fixed function pipeline

2008-07-27 Thread Stefan Dösinger
> This enables the replacement pretty much unconditionally... do we want > that? I'd say so, unless we have evidence that it's a bad idea to do enable it somewhere, and the drawback isn't fixable. > It also might make sense to give this its own file. It shares some code with the shader implementat

RE: [3/5] WineD3D: Optimize the fragment processing description

2008-07-27 Thread Stefan Dösinger
> Is there any particular reason you're not simply using the compiler's > support for bit-fields? Mostly because I've written this code before you mentioned them to me. I think it can't hurt to ask Alexandre if bitfields are ok to use in Wine. How's the support among compilers(older gcc versions? N

Re: IWineD3DDeviceImpl_SetRenderState

2008-07-27 Thread Jochen
Chris Ahrendt schrieb: [...] > h... I do know without the patch EQ2 doesn't run and with it it > then gets into the start of the game.. so it might be another one of > the if's... I can add the fog to the break with no if's...let me try > that. Right now I am running just the git 1.1.2+ tr

Re: [5/5] WineD3D: Implement an ARB_fragmen_program fixed function pipeline

2008-07-27 Thread H. Verbeet
2008/7/27 Stefan Dösinger <[EMAIL PROTECTED]>: > Unfortunately, even despite the preparations in the last patches, this patch > is still kinda huge because I have to replace all the fragment processing at > once. > This enables the replacement pretty much unconditionally... do we want that? It also

Re: [WideChar conversion improvements - 5/5] Add a lot of WideCharToMultiByte tests

2008-07-27 Thread Vitaliy Margolen
Colin Finck wrote: > Remove todo_wine from two tests, which now pass under Wine after the > changes in my previous patches. You have to do that in the patch that fixes the test. Each patch have to be autonomous and have all tests pass before and after it. Vitaliy.

Re: [3/5] WineD3D: Optimize the fragment processing description

2008-07-27 Thread H. Verbeet
Is there any particular reason you're not simply using the compiler's support for bit-fields?

Re: IWineD3DDeviceImpl_SetRenderState

2008-07-27 Thread Chris Ahrendt
Stefan Dösinger wrote: >> so valid values would be max = >> ALPHA(FF)RED(FF)GREEN(FF)BLUE(FF) > Which is the whole range of a DWORD. A DWORD is between 0 and 0x. So > the if check will never evaluate to true. (Also checking a DWORD for <0 is > redundant because a DWORD is unsigned,

Re: crypt32: Add test showing only file header is checked for cabinet files

2008-07-27 Thread Detlef Riekenberg
On Fr, 2008-07-25 at 11:28 -0700, Juan Lang wrote: > +/* Create a file with just the .cab header 'MSCF' */ > +file = CreateFileW( CreateFileW is not supported on win9x. (returned NULL with ERROR_CALL_NOT_IMPLEMENTED) I have a Patch ready for the other use of CreateFileW in dlls/crypt32/te

RE: IWineD3DDeviceImpl_SetRenderState

2008-07-27 Thread Stefan Dösinger
> so valid values would be max = > ALPHA(FF)RED(FF)GREEN(FF)BLUE(FF) Which is the whole range of a DWORD. A DWORD is between 0 and 0x. So the if check will never evaluate to true. (Also checking a DWORD for <0 is redundant because a DWORD is unsigned, thus never < 0) > I can chang

Re: IWineD3DDeviceImpl_SetRenderState

2008-07-27 Thread Chris Ahrendt
Stefan Dösinger wrote: >> + case WINED3DRS_FOGCOLOR: >> + /* Valid Values are between 0 and (4 bytes alpha, red, >> green, and blue)) */ >> + if ((Value >= 0) || >> + (Value <= 0x)) break; > Humm, this does not sound right to me. The fog color used to be

Re: IWineD3DDeviceImpl_SetRenderState

2008-07-27 Thread Chris Ahrendt
H. Verbeet wrote: > 2008/7/27 Chris Ahrendt <[EMAIL PROTECTED]>: >> Oh I also forgot... I believe that set render state is primarily called >> at the init of the app so should not overly effect the performance of >> the application. > Well, no, it pretty much gets called all the time. > >> +

Richedit: fix bug 14280, EM_SETTEXTTEX obeys ST_SELECTION with RTF inputs

2008-07-27 Thread Dustin Brody
I sent the patch at http://www.winehq.org/pipermail/wine-patches/2008-July/058460.html but got neither it applied nor any other comment. As far as I can tell, I complied with all the guidelines at http://www.winehq.org/site/sending_patches. Is it the editing of comments not strictly part of the ne

RE: IWineD3DDeviceImpl_SetRenderState

2008-07-27 Thread Stefan Dösinger
> + case WINED3DRS_FOGCOLOR: > + /* Valid Values are between 0 and (4 bytes alpha, red, > green, and blue)) */ > + if ((Value >= 0) || > + (Value <= 0x)) break; Humm, this does not sound right to me. The fog color used to be A8R8G8B8, thus equal values ar

Re: wined3d: universal surface convertor function for unsigned integer color formats(5th attempt)

2008-07-27 Thread Philip Nilsson
On Thu, Jul 24, 2008 at 08:14:40PM +0400, Victor Eremin wrote: > Supports conversion between most of "unsigned color" argb/xrgb > surface formats (D3DFMT_A8R8G8B8, D3DFMT_A8R3G3B2, etc), and > "luminosity" color formats (D3DFMT_L8, etc), > excluding D3DFMT_A16R16G16B16, D3DFMT_A8P8, D3DFMT_P8 and D

Re: IWineD3DDeviceImpl_SetRenderState

2008-07-27 Thread H. Verbeet
2008/7/27 Chris Ahrendt <[EMAIL PROTECTED]>: > Oh I also forgot... I believe that set render state is primarily called > at the init of the app so should not overly effect the performance of > the application. Well, no, it pretty much gets called all the time. > + /* Valid Values are betw

Re: IWineD3DDeviceImpl_SetRenderState

2008-07-27 Thread Chris Ahrendt
Stefan Dösinger wrote: >> /* >> * Get / Set Render States >> * TODO: Verify against dx9 definitions >> * > As Henri said, this needs a test case. So far we have not found any Set* > function that returns an error. For SetTexture, SetSamplerState, ..., if the > sampler index is out of boun

Re: IWineD3DDeviceImpl_SetRenderState

2008-07-27 Thread Chris Ahrendt
Stefan Dösinger wrote: >> /* >> * Get / Set Render States >> * TODO: Verify against dx9 definitions >> * > As Henri said, this needs a test case. So far we have not found any Set* > function that returns an error. For SetTexture, SetSamplerState, ..., if the > sampler index is out of boun

Re: wined3d: universal surface convertor function for unsigned integer color formats(5th attempt)

2008-07-27 Thread Victor
Well, the last attempt (with added big-endian support) was submitted several days ago, and again - no feedback, and patch still isn't accepted. What's wrong with patch now? --- Victor Eremin signature.asc Description: This is a digitally signed message part.

Re: Bizarre idea: creating our own extension to msi for cross-platform installers

2008-07-27 Thread Scott Ritchie
Stefan Dösinger wrote: >> What if we created a standard for passing some sort of wine-specific >> metadata in an MSI file? Windows would ignore it, but application >> developers could use it to include some helpful Linux-specific Wine >> instructions like what windows version to use, a custom .des

Re: IWineD3DDeviceImpl_SetRenderState

2008-07-27 Thread John Klehm
On Sun, Jul 27, 2008 at 7:59 AM, Chris Ahrendt <[EMAIL PROTECTED]> wrote: > I removed the documentation I just put it in there for this so people can > understand what was done... it is removed > Documentation is a good thing. You just can't use the exact same wording from a copyrighted source (M

RE: Bizarre idea: creating our own extension to msi for cross-platform installers

2008-07-27 Thread Stefan Dösinger
> What if we created a standard for passing some sort of wine-specific > metadata in an MSI file? Windows would ignore it, but application > developers could use it to include some helpful Linux-specific Wine > instructions like what windows version to use, a custom .desktop file, > or even instru

RE: IWineD3DDeviceImpl_SetRenderState

2008-07-27 Thread Stefan Dösinger
> /* > * Get / Set Render States > * TODO: Verify against dx9 definitions > * As Henri said, this needs a test case. So far we have not found any Set* function that returns an error. For SetTexture, SetSamplerState, ..., if the sampler index is out of bounds, the native implementation hap

Re: ole32: fix a bad return value for DefaultHandler_SetExtent

2008-07-27 Thread Rob Shearman
2008/7/26 <[EMAIL PROTECTED]>: > fix a bad return value for DefaultHandler_SetExtent implemented in > defaulthandler.c > > ChangeLog entry: > * real name : François DORIN > * email : [EMAIL PROTECTED] > * description : when the server is running, the return value must be the > value of the deleg

Re: ole32: fix offsets managment

2008-07-27 Thread Rob Shearman
2008/7/26 <[EMAIL PROTECTED]>: > It's my first patch. So, if something is wrong, don't hesitate to notify me ! > > ChangeLog entry : > * real name : François DORIN > * email : [EMAIL PROTECTED] > * description : offsets can be negative. It is necessary to treat them as > signed numbers to

Re: IWineD3DDeviceImpl_SetRenderState

2008-07-27 Thread James McKenzie
Chris Ahrendt wrote: > H. Verbeet wrote: > >> 2008/7/27 Chris Ahrendt <[EMAIL PROTECTED]>: >> >>> I did not copy and paste from MSDN.. I used the rules defined in the >>> statelemt.. I can remove the comment if that is what you are talking >>> about? But the code itself I did myself... >>>

Re: IWineD3DDeviceImpl_SetRenderState

2008-07-27 Thread Chris Ahrendt
H. Verbeet wrote: > 2008/7/27 Chris Ahrendt <[EMAIL PROTECTED]>: >> I did not copy and paste from MSDN.. I used the rules defined in the >> statelemt.. I can remove the comment if that is what you are talking >> about? But the code itself I did myself... >> > Documentation is copyrighted. I removed

Re: Bizarre idea: creating our own extension to msi for cross-platform installers

2008-07-27 Thread Reece Dunn
2008/7/27 Scott Ritchie <[EMAIL PROTECTED]>: > Just a crazy thought, but... > > What if we created a standard for passing some sort of wine-specific > metadata in an MSI file? Windows would ignore it, but application > developers could use it to include some helpful Linux-specific Wine > instructi

Re: Bizarre idea: creating our own extension to msi for cross-platform installers

2008-07-27 Thread Markus Hitter
Am 27.07.2008 um 10:39 schrieb Scott Ritchie: > This way, a single .msi file could be a true universal installer for > both Windows machines and Linux machines. This is a good idea. However, if developers intentionally develop for Wine they can easily go a step further and build a native Linux

Re: IWineD3DDeviceImpl_SetRenderState

2008-07-27 Thread H. Verbeet
2008/7/27 Chris Ahrendt <[EMAIL PROTECTED]>: > I did not copy and paste from MSDN.. I used the rules defined in the > statelemt.. I can remove the comment if that is what you are talking > about? But the code itself I did myself... > Documentation is copyrighted.

Re: IWineD3DDeviceImpl_SetRenderState

2008-07-27 Thread H. Verbeet
> --- device_old.c2008-07-25 11:42:25.0 -0400 > +++ device.c2008-07-26 21:07:45.0 -0400 Unrelated to the patch, but if you intend to work on Wine, I'd strongly recommend you setup git first. > +#define D3DBLEND_INVSRCCOLOR 4 You shouldn't use d3d8 or d3d9 definitions in win

Bizarre idea: creating our own extension to msi for cross-platform installers

2008-07-27 Thread Scott Ritchie
Just a crazy thought, but... What if we created a standard for passing some sort of wine-specific metadata in an MSI file? Windows would ignore it, but application developers could use it to include some helpful Linux-specific Wine instructions like what windows version to use, a custom .desktop

re: ole32: fix offsets managment

2008-07-27 Thread Dan Kegel
f.dorin at free.fr wrote: > It's my first patch. So, if something is wrong, don't hesitate to notify me ! > ... > + if (*(const WORD*)pFormat) pointer_desc = pFormat + *(const SHORT*)pFormat; Hi François! A few quick notes: 1) it's helpful if you can say what app each patch fixes, and what the sy