1. 22 Feb, 2016 1 commit
  2. 18 Feb, 2016 1 commit
  3. 04 Feb, 2016 1 commit
  4. 31 Jan, 2016 1 commit
  5. 29 Jan, 2016 1 commit
    • Berk Geveci's avatar
      Refactored and update the way algorithms are updated. · f020ebb6
      Berk Geveci authored
      The way algorithms were updated (made to execute) with
      request meta-data (such as update extent) was very error
      prone and counter-intuitive. Added new methods to make
      updating with meta-data easier. I also deprecated a number
      of methods to set request meta-data. This will encourage
      developers to migrate to the new API which is less error-
  6. 26 Jan, 2016 1 commit
  7. 22 Jan, 2016 1 commit
  8. 15 Jan, 2016 1 commit
  9. 03 Dec, 2015 1 commit
  10. 17 Nov, 2015 1 commit
  11. 13 Nov, 2015 1 commit
    • Ken Martin's avatar
      Update coincident geomtry support · 4be38a3f
      Ken Martin authored
      Add in support for specifying different offsets for surfaces
      lines and points. Update some example to remove the specified
      polydata value as the defaults are better.
      Update a valid image due to lighting changes
      Add a test that has points lines and surfaces all
      drawn on top of each other.
  12. 11 Nov, 2015 1 commit
  13. 23 Oct, 2015 1 commit
  14. 16 Oct, 2015 1 commit
    • Ken Martin's avatar
      Update multitouch support to be more general and robust · 26df1206
      Ken Martin authored
      The android multitouch events seem to be fairly buggy out of android
      so we have tried to make our handling of them more robust. At the same time
      move some of the multitouch methods into vtkRenderWindowInteractor as
      opposed to the architecture specific subclasses.
  15. 14 Oct, 2015 1 commit
  16. 09 Oct, 2015 2 commits
    • Ken Martin's avatar
      Fixes for samsung with linear interp · 84e8c707
      Ken Martin authored
      Samsung seems to have issues with 2D textures with linear interp
      in some cases.
    • Ken Martin's avatar
      Add android vr example and fixes to support it · c8fd8f3e
      Ken Martin authored
      This topic adds a volume rendering example to android builds.  It also
      fixes a number of issues to make it work with android including on
      Samsung devices which have a different OpenGL driver.
      VR use of 1D textures have been replaced with 2D textures as
      1D textures are not supported on OpenGL ES.
      Some minor build inprovements are included as well.
  17. 07 Oct, 2015 1 commit
  18. 25 Sep, 2015 1 commit
  19. 03 Sep, 2015 2 commits
    • Casey Goodlett's avatar
      Remove logging statements · 394633f8
      Casey Goodlett authored
    • Casey Goodlett's avatar
      Workaround problematic motion events · c3e55b81
      Casey Goodlett authored
      In some rare cases the action index may not be a index into
      getPointerId.  To workaround this issue do the following
      1) Change the semnatics of HandleMotionEvent to use the pointer id
      directly rather than looking up from index in C code.
      2) Wrap the java code in a try/catch to catch invalid motion events.
  20. 31 Aug, 2015 2 commits
    • Ken Martin's avatar
      Add PBO support into ES 3 builds and fix a warning · d38c65ba
      Ken Martin authored
      Add PBO support into OpenGL ES 3 builds
      Fix a warning on ES 2
    • Dan Lipsa's avatar
      COMP: Add logic to selectively use OpenGL or OSMesa. · f09903e4
      Dan Lipsa authored
      Use vtkOpenGL.cmake to decide to use (LINK_PRIVATE) OpenGL or Offscreen Mesa.
      OpenGL is now LINK_PRIVATE, so additional libraries and tests need to include OpenGL.
      Include the following in your CMakeLists.txt:
      for every ${module} that uses OpenGL. This takes care of include directories and
      linking of proper libraries.
  21. 27 Aug, 2015 1 commit
    • Ken Martin's avatar
      a number of ios and driod fixes · ea3731bf
      Ken Martin authored
      Made vtkFrameBufferObject be built for ES 2 as
      ES 2 does support it. This required a few changes.
      Made a number of fixes to the Android/IOS super build process. Fixed
      the install prefix to be pushed down to the subbuilds. Made a number
      of top level setting cached in the sub builds because they are cached
      there already and need to be overriden in the superbuild.  Otherwise
      top level changes did not propagate down.
  22. 26 Aug, 2015 1 commit
  23. 24 Aug, 2015 1 commit
  24. 21 Aug, 2015 1 commit
  25. 20 Aug, 2015 1 commit
    • Brad King's avatar
      ENH: Remove use of include <vtksys/ios/*> and vtksys_ios::* · 3ae7dd3a
      Brad King authored
      We no longer need this compatibility layer for the compilers we support.
      Use the following commands to switch to standard header and namespace:
       git grep -l vtksys/ios/ | xargs sed -i 's|vtksys/ios/||'
       git grep -l vtksys_ios | xargs sed -i 's|vtksys_ios|std|g'
  26. 05 Aug, 2015 1 commit
  27. 22 Jul, 2015 1 commit
    • Bill Lorensen's avatar
      STYLE: Replace vtksys_stl and vtksys_ios:: with std:: · 924248d9
      Bill Lorensen authored
      In the early days of VTK, support for stl was not portable. vtksys_stl
      and vtksys_ios provided a portable implementation of the stl. Now, all
      of the VTK supported compilers have portable stl implementations.
      This patch:
        1) Replaces the vtksys_ios:: with std::.
        2) Replaces the vtksys_stl:: with std::.
        3) Removes "using" statements for stl
  28. 14 Jul, 2015 1 commit
  29. 08 Jul, 2015 1 commit
  30. 02 Jul, 2015 1 commit
  31. 10 Jun, 2015 1 commit
  32. 26 May, 2015 1 commit
  33. 29 Apr, 2015 1 commit
  34. 09 Apr, 2015 1 commit
    • David C. Lonie's avatar
      Remove the RenderingFreeTypeOpenGL module. · 4f7460a5
      David C. Lonie authored
      This is not supported by the new OpenGL2 backend, and doesn't support
      new text features, like MathText, FontConfig, or custom font files.
      It only implements vtkTextMapper, which now will use a texture-based
      implementation, similar to vtkTextActor and friends.
  35. 06 Apr, 2015 1 commit
  36. 31 Mar, 2015 1 commit
    • Dan Lipsa's avatar
      Redesign "vtkGhostLevels" arrays and related ghost functionalties. · 4dee0274
      Dan Lipsa authored
      Co-authored-by: default avatarYuanxin Liu <leo.liu@kitware.com>
      Co-authored-by: Berk Geveci's avatarBerk Geveci <berk.geveci@kitware.com>
       -The semantics of each unsigned char in the ghost arrays changes:
        Instead of storing a numeric value representing how far a cell is
        from the boundary, it is now a bit field specified by
        vtkDataSetAttributes::CellGhostTypes and
        vtkDataSetAttributes::PointGhostTypes.  The bit field is consistent
        with VisIt specs.
      - Previously, filters strip all ghost cells they request from upstream
        before finalizing the output. This is no longer done.
      - vtkUniform grids previously supported blanking through member arrays
        vtkUniformGrid::CellVisibility and
        vtkUniformGrid::PointVisibility. These arrays are removed and the
        blanking functionality are supported through the new ghost arrays
      - the "vtkGhostLevel" arrays for cell and point data are renamed to
        vtkDataSetAttributes::GhostArrayName() ("vtkGhostType").
      - the version for VTK Legacy files is increased to 4.0 and the version for
        VTK XML files is increased to 2.0. When reading older files we
        convert vtkGhostLevels array to vtkGhostType.
  37. 29 Mar, 2015 1 commit