- 11 Jul, 2008 31 commits
-
-
Dylan Smith authored
-
Piotr Caban authored
-
Piotr Caban authored
msxml3: Fixed ISAXXMLReader_getContentHandler and ISAXXMLReader_getErrorHandler when second argument is NULL.
-
Piotr Caban authored
-
Detlef Riekenberg authored
-
Detlef Riekenberg authored
-
Detlef Riekenberg authored
-
Maarten Lankhorst authored
-
Michael Stefaniuc authored
-
Alexander Nicolaysen Sørnes authored
-
Alexander Nicolaysen Sørnes authored
-
Alexander Nicolaysen Sørnes authored
-
Andrew Talbot authored
-
Andrew Talbot authored
-
Andrew Talbot authored
-
Andrew Talbot authored
-
Andrew Talbot authored
-
Andrew Talbot authored
-
Andrew Talbot authored
-
Andrew Talbot authored
-
Andrew Talbot authored
-
Andrew Talbot authored
-
Andrew Talbot authored
-
Maarten Lankhorst authored
quartz: Make the file source rotate around the 'first' sample, to prevent starvation of a single stream. This prevents the file source from starving a single thread off.
-
Maarten Lankhorst authored
-
H. Verbeet authored
Destroying the stateblock potentially references the shader backend. If the stateblock has active shaders when it is released, the shader's destructor will tell the shader backend to destroy the corresponding resources. This was exposed by my patch that moved the glsl program lookup table into the backend's private data.
-
Juan Lang authored
wintrust: Use path in WIN_TRUST_SUBJECT_FILE structure rather than assuming a path is passed in place of WINTRUST_DATA's pFile member.
-
Nikolay Sivov authored
-
Nikolay Sivov authored
-
Nikolay Sivov authored
-
Zac Brown authored
-
- 10 Jul, 2008 9 commits
-
-
Alexandre Julliard authored
-
H. Verbeet authored
Calling shader_select() from inside depth_blt() isn't necessarily safe. shader_select() assumes CompileShader() has been called for the current shaders, but that depends on STATE_VSHADER / STATE_PIXELSHADER being applied. That isn't always true when depth_blt() gets called, with the result that sometimes GLSL programs could be created with no shader objects attached.
-
Alistair Leslie-Hughes authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Dylan Smith authored
The uncommon case that this patch handles is enough whitespace being on the first line of a paragraph to cause it to wrap. In this case the first non-space character will be wrapped onto the next line.
-
Dylan Smith authored
Runs that are skipped over still need to affect the wrapping position, otherwise they won't affect further run positions.
-
Dylan Smith authored
-
Dylan Smith authored
Lines in ME_WrapHandleRun were removed because ME_CalcRunExtent is already called unconditionally just before it in the call to ME_WrapSizeRun.
-