1. 29 Oct, 2013 1 commit
  2. 25 Jan, 2013 1 commit
  3. 14 Dec, 2012 1 commit
    • Yuanxin Liu's avatar
      vtkThreshold: Add continuous range option · 052a9ef1
      Yuanxin Liu authored
      Previous vtkThreshold considers the scalars from each cell as a
      discrete set. A new option is added that considers the scalars as a
      continuous interval instead, where the lower bound is the minimum
      scalar value and the upper bound is the maximum. This has the effect
      of producing more cells when AllScalar is set to be 0: A narrow
      threshold might not contain any scalar from the vertices, but it can
      still intersect the scalar interval.
      
      Change-Id: I32253e6f4c1ac892010b38ecdcad17e013b133b9
      052a9ef1
  4. 12 Jun, 2012 1 commit
    • Kyle Lutz's avatar
      Fix misspelling for SetOutputPointsPrecision() · b1441223
      Kyle Lutz authored
      This fixes a spelling error in the SetOutputPointsPrecision() method
      signature. Also fixes a small misspelling in the documentation for
      the Set/GetOutputPointsPrecision() methods.
      
      This fixes VTK bug #13237.
      
      Change-Id: If53e52067654262c2e8feb2d94a07009b4b7a57b
      b1441223
  5. 14 May, 2012 1 commit
    • Kyle Lutz's avatar
      Add API to allow users to set desired output point precision · 49d1f124
      Kyle Lutz authored
      This adds new API to a few of the vtkAlgorithm sub-classes which
      allows the user to decide what level of floating-point precision
      they want for the vtkPoint's object in the output data set. By
      default these algorithms will output points with a precision equal
      to that of the input data set. Alternatively the user may instruct
      the algorithm to always use single-precision or double-precision.
      
      Change-Id: I1c6b8ca854ff8da1bae5415e2d4c33fbfbaf1153
      49d1f124
  6. 09 Apr, 2012 2 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
      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
  7. 10 Feb, 2011 2 commits
  8. 08 Feb, 2011 1 commit
  9. 07 Feb, 2011 1 commit
    • David E. DeMarle's avatar
      Make prioritization handle more than one array. · 06a0f094
      David E. DeMarle authored
      I now attach the name of each array to the range information for it. I then
      use the name of the current ArrayToProcess instead of the old-school active
      Scalars to find the right range in the Contour and Threshold filters.
      
      Change-Id: Ib0437992464f4f665178ff60986e87e5633e35d0
      06a0f094
  10. 20 May, 2010 1 commit
    • Mark Olesen's avatar
      Remove vtk(Cxx|Type)RevisionMacro · ecbbf7f7
      Mark Olesen authored
      The CVS $Revision$ keyword replacement will no longer maintain these
      macros automatically.  They were used only to implement CollectRevisions
      and vtkObjectBase::PrintRevisions, an API that was never used.
      
      Automated as follows:
      
        pass 0:
        catch templates
        ---------------
        $ git grep 'vtk\(Cxx\|Type\)RevisionMacro' | grep '<'
      
        pass 1:
        main changes
        ---------------
        $ git grep -l '^vtkCxxRevisionMacro' | while read file; do
          echo "$file" 1>&2
          perl -i -ne 'print unless (/^vtkCxxRevisionMacro/ and /\)/)' $file
        done
        $ git grep -l -e 'vtkTypeRevisionMacro(' | while read file; do
          echo "$file" 1>&2
          perl -i -pe 's/vtkTypeRevisionMacro/vtkTypeMacro/g' $file
        done
      
        pass 2:
        verify
        ---------------
        $ git grep 'vtk\(Cxx\|Type\)RevisionMacro'
      
      Fixed multi-line vtkCxxRevisionMacro and templates by hand.
      ecbbf7f7
  11. 19 May, 2010 1 commit
  12. 23 Apr, 2010 1 commit
    • Mark Olesen's avatar
      Remove vtk(Cxx|Type)RevisionMacro · 19c55e0e
      Mark Olesen authored
      The CVS $Revision$ keyword replacement will no longer maintain these
      macros automatically.  They were used only to implement CollectRevisions
      and vtkObjectBase::PrintRevisions, an API that was never used.
      
      Automated as follows:
      
        pass 0:
        catch templates
        ---------------
        $ git grep 'vtk\(Cxx\|Type\)RevisionMacro' | grep '<'
      
        pass 1:
        main changes
        ---------------
        $ git grep -l '^vtkCxxRevisionMacro' | while read file; do
          echo "$file" 1>&2
          perl -i -ne 'print unless (/^vtkCxxRevisionMacro/ and /\)/)' $file
        done
        $ git grep -l -e 'vtkTypeRevisionMacro(' | while read file; do
          echo "$file" 1>&2
          perl -i -pe 's/vtkTypeRevisionMacro/vtkTypeMacro/g' $file
        done
      
        pass 2:
        verify
        ---------------
        $ git grep 'vtk\(Cxx\|Type\)RevisionMacro'
      
      Fixed multi-line vtkCxxRevisionMacro and templates by hand.
      19c55e0e
  13. 10 Nov, 2009 1 commit
  14. 24 Sep, 2009 1 commit
    • David E. DeMarle's avatar
      ENH: Add concept of Resolution to the pipeline. · 4dbfb416
      David E. DeMarle authored
      You can now request data at a particular resolution. Do so by having the
      sink call SetUpdateResolution(0.0->1.0) in the same way that it calls
      SetUpdateExtent to ask for a particular piece. Similar to the way time
      works, this new request goes up the pipeline to the source which can respect
      the request or not, and returns an answer in the form of a DATA_RESOLUTION
      key in its produced DataObject.
      4dbfb416
  15. 17 Feb, 2008 1 commit
  16. 08 May, 2006 1 commit
  17. 02 May, 2006 1 commit
  18. 21 Apr, 2005 1 commit
  19. 30 Dec, 2004 1 commit
  20. 30 Sep, 2004 1 commit
  21. 21 Sep, 2004 1 commit
  22. 19 Dec, 2003 1 commit
  23. 05 Dec, 2003 1 commit
  24. 14 Nov, 2003 1 commit
  25. 07 Nov, 2003 1 commit
  26. 05 Nov, 2003 1 commit
  27. 16 Dec, 2002 1 commit
  28. 03 Sep, 2002 1 commit
  29. 22 Jan, 2002 1 commit
  30. 04 Jan, 2002 1 commit
    • Brad King's avatar
      ENH: Three sweeping changes. · 12947cd1
      Brad King authored
      1.) vtkTypeRevisionMacro is now used in all VTK classes in place of
          vtkTypeMacro.  It invokes the original vtkTypeMacro and then adds
          a protected CollectRevisions method for future use in serialization.
          A corresponding vtkCxxRevisionMacro has been added to every .cxx file
          to implement the CollectRevisions method for each class.  This will
          allow collection of every class revision at run time.  Any new VTK class
          should use vtkTypeRevisionMacro instead of vtkTypeMacro.  The .cxx
          implementation should then have the following line:
            vtkCxxRevisionMacro(vtkFoo, "$Revision: 1.1 $");
          CVS should insert the correct revision number when the class is commited.
      
      2.) vtkTypeMacro now also adds a typedef called "Superclass" to refer to
          the superclass of any VTK class.  All PrintSelf methods have been
          updated to call their superclass's PrintSelf like this:
            this->Superclass::PrintSelf(os,indent);
          This should reduce the number of places that refer to a superclass
          by its actual name.
      
      3.) The standard ::New() method implementation has been replaced with a
          macro.  Instead of an explicitly written implementation to try the
          object factory and then call the new operator, VTK classes should
          instead use the following macro unless they have a special New() method:
            vtkStandardNewMacro(vtkFoo);
          This will implement the New() method in the standard way.  The line
          should appear in the .cxx implementation file, not in the header.
          Using the macro will make it easier to change the standard
          implementation of the method.
      
      Also removed tabs from many files.
      12947cd1
  31. 10 Dec, 2001 1 commit
  32. 05 Dec, 2001 1 commit
  33. 29 Nov, 2001 1 commit
  34. 13 Nov, 2001 1 commit
  35. 02 Nov, 2001 1 commit
  36. 29 Aug, 2001 1 commit
  37. 10 Aug, 2001 1 commit
  38. 02 Jul, 2001 1 commit