1. 29 Aug, 2014 1 commit
  2. 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
  3. 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
  4. 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
  5. 10 Jun, 2008 2 commits
    • Berk Geveci's avatar
      BUG: Fixed crash. · 4a5f0120
      Berk Geveci authored
      It turns out that the XML reader calls GetNumberOfPoints() during RequestInformation().
      Therefore, this cannot be obtained from the output data (because it is not populated).
      Previously, the hyperoctree reader was returning 0. With my last change, it started
      crashing because output is now NULL. Changed to return 0 if output is NULL. This
      is not the right behaviour because meta-data gets the wrong number of points.
      However, there is no easy way to compute the number of points/cells without actually
      reading the data so it stays.
      4a5f0120
    • Berk Geveci's avatar
      BUG: Fixed problems left over from the old pipeline code. · d7db1414
      Berk Geveci authored
      The readers were accessing their output information and through the executive.
      This creates problems when what is passed to ProcessRequest() is different.
      d7db1414
  6. 05 Jan, 2006 1 commit
    • Utkarsh Ayachit's avatar
      ENH: · fad86463
      Utkarsh Ayachit authored
      * vtkDataArray now has a new superclass-vtkAbstractArray.vtkAbstractArray
      provides type-agnostic API to access array elements. vtkDataArray provides
      a double API to access values -- such an API is deliberately missing from
      vtkAbstractArray, since arrays like string arrays are not castable to doubles.
      
      * vtkAbstractArray has the notion of components/tuples, but does not make
      any assumptions about the arragment of these. It's up to the concrete
      subclasses how the data is represented in memory.
      
      * vtkFieldData used to provide tuple API to get/set values from data arrays
      contained in it. However, now that FieldData can have arrays that are not
      vtkDataArrays, this API is not longer valid.
      The following are the methods that are no longer available:
      double* GetTuple(const vtkIdType);
      void SetTuple(const vtkIdType i, const double* tuple);
      void GetTuple(const vtkIdType i, double* tuple);
      void InsertTuple(const vtkIdType i, const double* tuple);
      void InsertNextTuple(cons double*);
      double GetComponent(const vtkIdType i, const int j);
      void SetComponent(const vtkIdType i, const int j, const double c);
      void InsertComponent(const vtkIdType i, const int j, const double c);
      However, new API is provided to copy tuples arround from one field data to
      another using:
      void SetTuple(const vtkIdType i, const vtkIdType j, vtkFieldData* source);
      void InsertTuple(const vtkIdType i, const vtkIdType j, vtkFieldData* source);
      vtkIdType InsertNextTuple(const vtkIdType j, vtkFieldData* source);
      
      * vtkFieldData provide a vtkDataArray* GetArray(int index) to retrieve arrays
      in the field data. This function can will now return a NULL if the array
      at the given index is not a data array. It provides
      vtkAbstractArray* GetAbstractArray(int index);
      to retrieve an array even if it isn't a vtkDataArray.
      
      * Since vtkFieldData can contain arrays that aren't subclasses of
      vtkDataArray, so can vtkDataSetAttributes. However, an attribute can only be
      a vtkDataArray subclass i.e. one cannot set a vtkStringArray as the SCALARS
      array for a Point Data, for example.
      
      * String Array IO is only supported in XML file formats. If deemed important,
      support may be added for lecacy file formats.
      
      *** Array Iterators ***
      Another addition to the VTK Arrays, is the notion of Array Iterator. A
      vtkArrayIterator subclass is be provided for every vtkAbstractArray
      subclass. The iterator is a random access iterator. The iterators are not
      available in any of the wrapped languages, however, in C++ they can be used to
      write templatized code to processes the array values without any implicit type
      conversion and consequent loss of precision. vtkArrayIteratorTemplateMacro is
      provided to simply switching between different types of the arrays. Examples of
      use of this macro and the iterators can be found in
      vtkXMLWriter.cxx / vtkXMLDataReader.cxx / vtkXMLStructuredDataReader.cxx.
      fad86463
  7. 27 Sep, 2005 2 commits
  8. 26 Sep, 2005 1 commit