wined3d: Update a comment.

shader_select takes care of compiling the shader since we have the shader duplication infrastructure. However, there's still a motivation to skip the shader_select call if the vertex shader is dirty.

wined3d: Update a comment.
3fbdb642 · Stefan Dösinger · Alexandre Julliard · 703dcca6 · 3fbdb642
Commit 3fbdb642 authored Feb 23, 2009 by Stefan Dösinger Committed by Alexandre Julliard Mar 30, 2009
Show whitespace changes
Inline Side-by-side

Showing with 2 additions and 2 deletions

arb_program_shader.c dlls/wined3d/arb_program_shader.c +2 -2

No files found.
--- a/dlls/wined3d/arb_program_shader.c
+++ b/dlls/wined3d/arb_program_shader.c
@@ -3045,8 +3045,8 @@ static void fragment_prog_arbfp(DWORD state, IWineD3DStateBlockImpl *stateblock,
     * type overwrites GL_ARB_fragment_program. This is currently the case with GLSL. If we really want to use
     * atifs or nvrc pixel shaders with arb fragment programs we'd have to disable GL_FRAGMENT_PROGRAM_ARB here
     *
-     * Don't call shader_select if the vertex shader is dirty, because some shader backends(GLSL) need both shaders
-     * to be compiled before activating them(needs some cleanups in the shader backend interface)
+     * Don't call shader_select if the vertex shader is dirty, because it will be called later on by the vertex
+     * shader handler
     */
    if(!isStateDirty(context, device->StateTable[STATE_VSHADER].representative)) {
        device->shader_backend->shader_select((IWineD3DDevice *)stateblock->wineD3DDevice, use_pshader, use_vshader);