From b0b9a11c65bea6a8985426b4630983ab6b74ed23 Mon Sep 17 00:00:00 2001 From: David Rose Date: Fri, 17 May 2002 18:01:06 +0000 Subject: [PATCH] fix comment --- panda/src/glgsg/glGraphicsStateGuardian.cxx | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/panda/src/glgsg/glGraphicsStateGuardian.cxx b/panda/src/glgsg/glGraphicsStateGuardian.cxx index be078a30a0..ae216ca647 100644 --- a/panda/src/glgsg/glGraphicsStateGuardian.cxx +++ b/panda/src/glgsg/glGraphicsStateGuardian.cxx @@ -3513,13 +3513,13 @@ set_blend_mode(ColorWriteAttrib::Mode color_write_mode, case TransparencyAttrib::M_alpha: case TransparencyAttrib::M_alpha_sorted: case TransparencyAttrib::M_dual: - // Should we really have an "alpha" and an "alpha_sorted" mode, - // like Performer does? (The difference is that "alpha" is with - // the write to the depth buffer disabled.) Or should we just use - // the separate depth write transition to control this? Doing it - // implicitly requires a bit more logic here and in the state - // management; for now we require the user to explicitly turn off - // the depth write. + // Should we really have an "alpha" and an "alpha_sorted" + // mode, like Performer does? (The difference is that + // "alpha_sorted" is with the write to the depth buffer + // disabled.) Or should we just use the separate depth write + // transition to control this? Doing it implicitly requires a + // bit more logic here and in the state management; for now we + // require the user to explicitly turn off the depth write. enable_multisample_alpha_one(false); enable_multisample_alpha_mask(false); enable_blend(true);