1. 18 Jun, 2009 5 commits
  2. 17 Jun, 2009 1 commit
  3. 16 Jun, 2009 5 commits
  4. 15 Jun, 2009 1 commit
  5. 12 Jun, 2009 3 commits
  6. 11 Jun, 2009 3 commits
  7. 10 Jun, 2009 2 commits
  8. 08 Jun, 2009 2 commits
  9. 05 Jun, 2009 3 commits
  10. 04 Jun, 2009 5 commits
  11. 03 Jun, 2009 3 commits
  12. 02 Jun, 2009 5 commits
  13. 29 May, 2009 2 commits
    • fogal1's avatar
      Invalidate the transparency cache earlier. · c3c6e49c
      fogal1 authored
      In some cases, we'd render earlier than expected, before getting
      through RenderSetup.  The cache would be at it's old value then
      (except on first renderings!), and wouldn't know to recalculate.
      By invalidating here, we'll force this to get recalculated if some
      code needs to know about transparencies before RenderSetup
      completes.
      
      AFAICT, this also means that `simple' re-renders, such as rotating
      the volume, will cause the calculation (and ensuing global
      communication) to occur.  This is undesirable, but no worse than a
      week ago.
      
      git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@7441 18c085ea-50e0-402c-830e-de6fd14e8384
      c3c6e49c
    • fogal1's avatar
      Make an image dump happen sooner. · 90f0665f
      fogal1 authored
      It was giving misleading results before.  We were dumping images
      after we did our opaque composite, but also after we'd broadcast
      out the resultant image to image-less nodes.  This meant that
      nodes that didn't render anything looked as if they rendered the
      entire volume.
      
      git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@7440 18c085ea-50e0-402c-830e-de6fd14e8384
      90f0665f