1. 05 Mar, 2015 1 commit
    • Ken Martin's avatar
      A number of transparency related issues fixed · 944ee020
      Ken Martin authored
      A few good fixes in here that are all related. The biggest is a
      fix to OpenGLActor to use the more comprehensive GetIsOpaque
      method in determining if an actor is opaque. The old code only
      looked at the property's opacity. This is why you would see folks
      setting somethings opacity to 0.99 to get it treated as translucent
      because the actor code wasn't handling it correctly. This change
      resulted in 3 new valid images for tests that were rendering
      translucent items as if they were opaque. I removed these tests
      from the old backend as I did not want to change the behavior
      for that backend.
      
      Next up is depth peeling. OpenGL2 depth peeling would render
      a number of peels up to the limit and then just stop. Any geometry
      left between the opaque layer and the last translucent layer was
      just thrown out.  This created very noticable artifacts and was bad.
      This change makes it so that when it gets to the last pass, it will
      render all remaining geometry using alpha blending. This is much
      better. Fix example if you get the limit to 20 layers and 20 was
      not enough to render all the geometry, this change renders 19
      layers using depth peeling, then in the 20th render it would add
      in all the remaining geometry as last layer. That last layer may
      have overlapping geometry which is rendered using alpha blending.
      
      Finally some changes to the PointGaussianMapper. It turns out that
      the point gaussian mapper is an translucent mapper which means it
      needs the first change, and it is a very tough case for depth peeling
      resulting in the second change. While at it I modified this mapper
      to render far fewer fragments, resulting is far fewer overlapping
      layers and fewer artifacts. Really when using PointGaussian you
      should turn off depthpeeling as it is not needed and actually makes
      it worse, but these changes will make it better if you happen to have
      it on.  Also cleaned up the mapper so that the radius is equal to
      the standard devisation of the gaussian, previously it was four
      standard deviations.
      
      Change-Id: I62d90b6e424ac0e939033387ed10ba8caac66095
      944ee020
  2. 18 Dec, 2014 1 commit
  3. 10 Sep, 2014 1 commit
  4. 03 Jul, 2014 1 commit
    • Ben Boeckel's avatar
      modules: add modules to "kits" · e5203447
      Ben Boeckel authored
      The main kits are:
      
          vtkCommon
          vtkFilters
          vtkIO
          vtkImaging
          vtkInteraction
          vtkOpenGL (required due to a dependency cycle from
                     vtkRenderingOpenGL on vtkImagingHybrid)
          vtkParallel
          vtkRendering
          vtkViews
          vtkWrapping
      
      Modules which deal with a specialization of another module belong to the
      kit related to the specialization (i.e., FiltersParallel and
      IOParallelXML both belong to the vtkParallel kit) to avoid circular
      dependencies that arise when put into the same kit as the "lesser"
      module.
      
      Change-Id: Icae0baa78d62cc0dcce84546541df600d4f311dd
      e5203447
  5. 16 Apr, 2014 2 commits
  6. 12 Nov, 2013 1 commit
  7. 04 Jun, 2013 1 commit
    • Brad King's avatar
      Convert VTKData test inputs to ExternalData content links · 3797f83d
      Brad King authored
      Add to the Testing/Data directory ExternalData content links mirroring
      the content and layout we use from the VTKData/Data directory.
      
      Add a CMake/vtkLegacyData.cmake module, included from CMakeLists.txt and
      Testing/External/CMakeLists.txt, to call ExternalData_Expand_Arguments
      for all data directories added from VTKData/Data.  This will bulk-fetch
      all test input data currently used by tests of any module, enabled or
      not.  We can make the DATA{} references more granular later.
      
      Add a VTK_TEST_DATA_DIR variable to refer to the directory we tell the
      ExternalData module to populate the real data files.  Replace references
      to VTK_DATA_ROOT in test command lines (after -D) with references to
      VTK_TEST_DATA_DIR.  Drop the VTK_DATA_ROOT CMake option and stop using
      the VTKData repository.
      
      Remove the TESTING_DATA option from the vtk_add_test_cxx API and remove
      the VTK_DATA_ROOT option from the vtk_add_test_mpi API since all test
      input data are now handled through ExternalData and Testing/Data content
      links.
      
      Change-Id: Id02490b76ea2e161b9038188264a4830485039d8
      3797f83d
  8. 31 May, 2013 1 commit
  9. 17 May, 2013 2 commits
  10. 14 May, 2013 1 commit
  11. 28 Apr, 2013 1 commit
    • Andrew Maclean's avatar
      These Python tests have been refactored. · 3810c5a6
      Andrew Maclean authored
      This has been done by removing the "tcl-isms" and making
       the code more readable. In some cases redundant code
       has been removed (often a result of copy/paste operations).
       The code has also been checked to ensure each line is 80
       characters or less.
      
      The code can now be run using vtkpython or by using the
       appropriate Python environment.
      
      Originally these were TCL scripts that were converted using
        vtkTclTestToPy.py and they they needed to be run through the
        rtImageTest.py driver which defines a few needed
        functions/variables for their operation. To this end
        backdrop.py has been added where it is needed.
      
      Change-Id: I50d6505628c140ea4551f74f7f3e85df907567e1
      Signed-off-by: Andrew Maclean's avatarAndrew Maclean <andrew.amaclean@gmail.com>
      3810c5a6
  12. 15 Feb, 2013 1 commit
    • Bill Lorensen's avatar
      ENH: Tcl tests should not fail if VTK_DATA_ROOT is missing. · c5ab6fda
      Bill Lorensen authored
      A test should run without VTK_DATA_ROOT unless it needs input data
      from VTK_DATA_ROOT. Tests that have image baselines should still run
      unless they need input data.
      
      rtImage.tcl is modified to skip baseline comparisons if VTK_DATA_ROOT
      is not defined.
      
      CMakeLists.txt files are converted to use add_test_tcl macro for
      consistency.
      
      CMakeLists.txt files are changed to isolate tests that need input
      data.
      
      This was tested as follows:
      1) configured a build with VTK_DATA_ROOT undefine
         ctest -R Tcl-
         154 tests passed
      2) configured a build with VTK_DATA_ROOT defined
         ctest -R Tcl-
         390 tests passed
      
      This means that 390-154 = 236 tcl tests require input data
      
      Change-Id: I9067a3e3e2a710ddf353f0181cc7b22a85b5ef10
      c5ab6fda
  13. 11 Oct, 2012 1 commit
  14. 28 Aug, 2012 1 commit
  15. 09 Apr, 2012 4 commits
    • VTK Developers's avatar
      Remove trailing whitespace from all source files · 2d323fc4
      VTK Developers authored
      Exclude ThirdParty, Utilities/MetaIO, and Utilities/KWSys as these
      are maintained outside VTK.
      
      Co-Author: Marcus D. Hanwell <marcus.hanwell@kitware.com>
      Co-Author: Chris Harris <chris.harris@kitware.com>
      Co-Author: Brad King <brad.king@kitware.com>
      2d323fc4
    • VTK Developers's avatar
      Include module-wide headers and export macros · 144f03ca
      VTK Developers authored
      Include the module-wide header from every header in each module.
      Reference the export/visibility macro for the module.
      
      Co-Author: Marcus D. Hanwell <marcus.hanwell@kitware.com>
      Co-Author: Chris Harris <chris.harris@kitware.com>
      144f03ca
    • VTK Developers's avatar
      Add modular VTK build system · 0c1471f1
      VTK Developers authored
      Add module.cmake, CMakeLists.txt, and other build system files.
      
      The modular VTK build system is not yet mature.  The monolithic build
      files had a lot of infrastructure.  The modular build files reproduce
      much of the functionality but some features will need to be restored
      later.  Document status and tasks in "TODO-Modularization.txt".
      
      Co-Author: Marcus D. Hanwell <marcus.hanwell@kitware.com>
      Co-Author: Chris Harris <chris.harris@kitware.com>
      Co-Author: Brad King <brad.king@kitware.com>
      Co-Author: Nikhil Shetty <nikhil.shetty@kitware.com>
      0c1471f1
    • VTK Developers's avatar
      Modularize VTK tree layout · cdd4d6fd
      VTK Developers authored
      Move source files from their former monolithic VTK location to their new
      location in modular VTK without modification.  This preserves enough
      information for "git blame -M" and "git log --follow" to connect
      modularized VTK files to their original location and history.
      
      Co-Author: Marcus D. Hanwell <marcus.hanwell@kitware.com>
      Co-Author: Chris Harris <chris.harris@kitware.com>
      Co-Author: Brad King <brad.king@kitware.com>
      Co-Author: Nikhil Shetty <nikhil.shetty@kitware.com>
      cdd4d6fd