1. 27 Oct, 2015 1 commit
    • David Gobbi's avatar
      The vtkImageResliceMapper was needlessly recomputing. · af5d537c
      David Gobbi authored
      The ResliceNeedUpdate flag was not being reset after each update.  It
      looks like the developer (myself) was playing with this flag during a
      debugging session, and forgot to set it to the correct value before
      committing the code.
  2. 26 Oct, 2015 1 commit
  3. 18 Dec, 2014 1 commit
  4. 22 Oct, 2014 1 commit
    • David Gobbi's avatar
      Make streaming optional for the 3D image mappers. · 5e2432fb
      David Gobbi authored
      Previously, the default behavior of the 3D image mappers was to stream
      the data through the pipeline, meaning that only the part of the input
      image that was required to display one (possibly oblique) slice on the
      screen was updated.  However, this resulted in the UPDATE_EXTENT changing
      whenever a new slice was displayed, triggerring a pipeline update.
      The new default behaviour is to set the UPDATE_EXTENT to the WHOLE_EXTENT,
      so that the whole extent is updated on the first render, but no pipeline
      execution occurs on subsequent renders (e.g. while slicing through the data)
      unless the pipeline is modified.
      The StreamingOn() method can be used to revert to the old behavior.
      Change-Id: I76b31a2ae4b329885d755c2947b62f9a9474b88a
  5. 04 Sep, 2014 1 commit
  6. 03 Jul, 2014 1 commit
    • Ben Boeckel's avatar
      modules: add modules to "kits" · e5203447
      Ben Boeckel authored
      The main kits are:
          vtkOpenGL (required due to a dependency cycle from
                     vtkRenderingOpenGL on vtkImagingHybrid)
      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"
      Change-Id: Icae0baa78d62cc0dcce84546541df600d4f311dd
  7. 18 Jun, 2014 1 commit
    • Marcus D. Hanwell's avatar
      Moving rendering tests to more appropriate places · 7da0bc3d
      Marcus D. Hanwell authored
      Many of the OpenGL tests were for RenderingCore API, others were from
      RenderingImage and RenderingLabel. Moving them to more appropriate
      locations, this makes it easier to validate some of the OpenGL2
      implementations now we have a concept of multiple rendering backends.
      Change-Id: I48db6a50ddc3d64d899a6b99b8cd21960fa26055
  8. 02 May, 2014 1 commit
    • David Gobbi's avatar
      Add SetSlabModeToSum() to vtkImageResliceMapper. · 048419fb
      David Gobbi authored
      This change allows vtkImageResliceMapper to produce images that look
      like digitally reconstructed radiographs.  It required a new property
      to be added to vtkImageReslice, called ScalarScale, so that the output
      intensity can be appropriately scaled to the slab thickness, which is
      specified in physical units of distance (typically millimeters).  An
      existing test was modified in order to test this new feature.
      A ScalarShift property was also added for symmetry with ScalarScale,
      plus an OutputScalarType property so that vtkImageReslice can output a
      different scalar type than its input (useful for avoiding overflow with
      This change also fixes a performance issue that was introduced in August
      2011 when the SetInterpolator() method was added: that change caused the
      scalar conversion to always clamp to the limits of the output type, even
      when clamping was unecessary.  Now, clamping is only done when needed.
      Change-Id: I5e55db509e8ec537632a7a7e063a3bc0c50d9d20
  9. 12 Nov, 2013 1 commit
  10. 19 Jul, 2012 1 commit
    • Bill Lorensen's avatar
      BUG: Modules missing membership in StandAlone or Rendering. · 453a2f95
      Bill Lorensen authored
      The StandAlone + Rendering groups should contain what was in VTK
      before modularization without turning on additional flags.
      The StandAlone group is a special group of all modules that need no
      external dependencies, such as Boost, MPI, etc. It does include
      modules that rely on third party libraries VTK can build (by
      default). It DOES NOT include modules that depend on OpenGL. Those
      modules are in the Rendering group.
      Several modules that meet the above criteria for membership in the
      StandAlone group did not specify their membership via the GROUPS
      StandAlone property. Also, several modules were missing from the
      Rendering group.
      This topic was verified by building the VTK Wiki Examples:
      http://www.vtk.org/Wiki/VTK/Examples/Cxx against an installed VTK that
      was built with only the StandAlone and Rendering properties enabled.
      Change-Id: I8bbca22f44c087b0cbe9ff92ee2819a292b43da5
  11. 28 Apr, 2012 1 commit
    • David Gobbi's avatar
      BUG: Visibility was ignored for images in vtkImageStack. · 042ef264
      David Gobbi authored
      The visibility flag of members of the vtkImageStack was ignored.
      If a stack had only one member and if the vtkImageStack had a
      non-identity matrix, then the member's matrix was not reset
      correctly after the initial poke.
      Change-Id: If7246d5cc8cff3cc8bd3ad2cb143ba78141f173c
  12. 10 Apr, 2012 1 commit
    • David Gobbi's avatar
      ENH: Split new module InteractionImage from RenderingImage. · 75f84a7d
      David Gobbi authored
      The split allows RenderingImage to depend only on RenderingCore
      and ImagingCore.  The new InteractionImage module contains all of
      the ImageViewer classes, which depend on interaction and widgets.
      Change-Id: I927cb059a71c91d555086dcc9d61e8bea057dd83
  13. 09 Apr, 2012 5 commits
    • Marcus D. Hanwell's avatar
      Remove rendering modules from StandAlone · 478cd6ff
      Marcus D. Hanwell authored
      These should be in the Rendering group, but not StandAlone as they
      depend on OpenGL. We could possibly reintroduce the non-OpenGL modules
      at some point in the future if desired.
      Change-Id: I619be3fc3b3b48e8e0d9534cdb66bf1e329b9756
    • 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>
    • 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>
    • 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>
    • 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>