1. 09 Apr, 2015 2 commits
    • David C. Lonie's avatar
      Update baselines. · 1942a721
      David C. Lonie authored
    • 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.
  2. 06 Apr, 2015 2 commits
  3. 26 Mar, 2015 1 commit
    • Sean McBride's avatar
      Fixed memory leak in Cocoa code (regression) · acf0c227
      Sean McBride authored
      I accidently added a memory leak when adding partial ARC support.
      I forgot that one can build as mixed GC+MRR, in which case the
      explicit retain/release calls are needed, so added them back.
  4. 25 Mar, 2015 1 commit
  5. 16 Mar, 2015 2 commits
  6. 02 Mar, 2015 1 commit
  7. 26 Feb, 2015 1 commit
  8. 20 Feb, 2015 1 commit
    • Julien Finet's avatar
      Kill TDX timer when using no WindowHandle · ed304209
      Julien Finet authored
      From KillTimer(HWND hWnd, UINT_PTR uIDEvent) documentation:
      uIDEvent [in]: The timer to be destroyed. If the window handle passed to
      SetTimer is valid, this parameter must be the same as the nIDEvent value
      passed to SetTimer. If the application calls SetTimer with hWnd set to
      NULL, this parameter must be the timer identifier returned by SetTimer.
      Fixes #15334
      Change-Id: Ifd88c790f4955dcd352004e2f5cba22a900e02de
  9. 16 Feb, 2015 3 commits
  10. 13 Feb, 2015 1 commit
  11. 09 Feb, 2015 1 commit
    • Chris Harris's avatar
      Wait for resize notification in SetSize(...) · 39fedcd6
      Chris Harris authored
      Calling XSync(...) is not enough. This causes a timing issue
      went SetSize(...) is called following be a Render(...). In
      Render(...) the window is queried for the window size which
      will not have be resize yet so we get the old size! ( seen
      particularly in vtkWeb ). Add loop to wait for ConfigNotify
      event with the new size.
      Change-Id: I72d34cae16215b6887467496df23d7a8e0bdcd37
  12. 03 Feb, 2015 1 commit
  13. 19 Jan, 2015 1 commit
  14. 14 Jan, 2015 1 commit
  15. 18 Dec, 2014 3 commits
  16. 16 Dec, 2014 1 commit
    • Sean McBride's avatar
      Refactoring and cleanup of Cocoa NSWindow and NSView observations · 141198ec
      Sean McBride authored
      Now only perform observation at all if it was VTK that created the NSWindow/NSView.
      This avoids receiving many NSView frame change messages when not needed.
      Some renaming, new asserts, fix minor type mismatch.
      Things are more symmetrical now.
      Change-Id: I337afef3a07fe9e33abdfc6e7e714502262bcc91
  17. 12 Dec, 2014 1 commit
    • Utkarsh Ayachit's avatar
      Disable OpenGL error checks in release builds. · f1a90fd2
      Utkarsh Ayachit authored
      OpenGL error checks have been shown to affect performance dramtically
      when rendering large datasets. That being the case, this change adds a
      new flag which disables these checks in Release builds, by default.
      Users can still use the advanced variable
      VTK_REPORT_OPENGL_ERRORS_IN_RELEASE_BUILDS to enable checks in release builds as well.
      Change-Id: Ib7a46292fcbc9dd166dbbd6d9217ee71f98f14df
  18. 11 Dec, 2014 3 commits
    • Cory Quammen's avatar
      Enable coloring by indexed lookup for vtkStringArrays · 94498364
      Cory Quammen authored
      This change makes it possible to map vtkStringArrays to colors using
      indexed lookup mode. The vtkStringArrays may be associated with
      points, cells, or neither (field data). A slew of changes were
      required to give this capability:
      - Changed signature of vtkScalarsToColors::MapScalars(...) and
        vtkDiscretizableColorTransferFunction::MapScalars(...)  to take a
        vtkAbstractArray instead of a vtkDataArray. This enables mapping
        non-vtkDataArray arrays, such as vtkStringArrays. These changes are
        backwards compatible because vtkAbstractArray is the parent class of
      - Changed vtkLookupTable::MapScalarsThroughTable2(...) to handle
      - Changed vtkColorTransferFunction::MapScalarsThroughTable2(...) to handle
      - Added vtkAbstractMapper::GetAbstractScalars(...) that returns a data
        array as a vtkAbstractArray - needed to retrieve vtkStringArray
      - Added some error reporting when unhandled array type is encountered
        in vtkScalarsToColors::MapScalarsThroughTable2.
      - Enabled use of vtkStringArrays for coloring in the surface mappers.
      - Added some tests for mapping vtkStringArrays with
        vtkColorTransferFunction and vtkDiscretizableColorTransferFunction.
      - Added some tests for coloring objects by vtkStringArrays in cell data
        and point data.
      - Added logic to vtkMapper and vtkPolyDataMapper2D that generates a
        reasonable default lookup table when a vtkStringArray or other
        non-numeric array is selected for coloring by scalars. This requires
        making the vtkRenderingCore module depend on vtkCommonColor. Added
        tests for this feature.
      Change-Id: I91e2e451217139a7daabd7f4a63de0b8ff707ad4
    • Cory Quammen's avatar
      Handle coloring by field data · a07731a2
      Cory Quammen authored
      Some level of support was previously available for coloring by field
      data, but this was restricted to drawing triangle strips. This patch
      adds another mode to coloring by field data that enables coloring the
      entire data set by a particular tuple in the field data. The field
      data tuple gets mapped through the color map, and that color is used
      to color the entire data set. The default behavior for triangle strips
      is retained by setting this tuple index to -1, the default value.
      The motivation for this change is to make it possible to color blocks
      in a multi-block dataset according to a value in that block's field
      data array, e.g., an initial condition, block ID, etc. Vector values
      (arrays with more than one component) are fully supported.
      Several other improvements were also made:
      - Added test for existing capability of coloring by field data.
      - Added test for coloring by tuple of field data.
      - Modified vtkMapper::GetScalarModeAsString() to return
        string for field data scalar mode.
      - Fixed vtkDataSetSurfaceFilter::UnstructuredGridExecute(...) and
        to pass field data through to output
      Change-Id: I0d97e84ec77e7ea01ca1b1350acce73cb6c4c15b
    • Sean McBride's avatar
      Unified mixed unsigned char/int usage to bool · b54bce1d
      Sean McBride authored
      Fixes -Wconversion warnings that pointed out the mixed use of
      unsigned char and int in these APIs.
      Switched to bool since the comments describe it as a 'flag'
      This is an API change, but shouldn't cause much trouble I hope.
      Change-Id: I0ded5ea638c646f9e5c7aa792fe93784cb9025b4
  19. 03 Dec, 2014 1 commit
    • Sean McBride's avatar
      Only react to NSView frame changes if VTK itself created the NSView · fca2fd59
      Sean McBride authored
      Without this, VTK will change the size of the NSWindow, which apps
      that create their own NSView and NSWindow and merely use VTK to draw into
      them might not want/expect.
      Fixes a regression I added in I3eb86e9982caae464fffe1c8cfc19035a194ec27
      related to bug #14266.
      Also added a public getter for the ViewCreated flag.
      Also use getters in PrintSelf, since everything there was done getters.
      Change-Id: I13ede32d361f9b17e11b8b0b37ad1997a864bf40
  20. 28 Nov, 2014 1 commit
  21. 26 Nov, 2014 2 commits
  22. 25 Nov, 2014 2 commits
  23. 24 Nov, 2014 1 commit
  24. 20 Nov, 2014 1 commit
    • Sean McBride's avatar
      Added partial/initial support for Cocoa ARC memory management · dd3f20db
      Sean McBride authored
      Did this by creating #defines indicating if GC, MRR, or ARC, then excluding
      retain/release/autorelease as necessary in the non-MRR case.
      For the MRR case, there is really no change here.
      For the GC case, retain/release/autorelease are nop at runtime,
      but now they are excluded at compile time, so significant change.
      For ARC, this fixed some (but not all) compiler errors, since
      retain/release/autorelease cannot be called explicitly, and now aren’t.
      Also fixed clang static analyzer (false positive) warning by reworking
      memory management in InternalCreateTimer()/InternalDestroyTimer() a bit.
      All this is necessary but insufficient. More to come.
      Change-Id: I5666a01d8ed258c63f5415e4a381ea629a12ec7a
  25. 19 Nov, 2014 1 commit
  26. 04 Nov, 2014 1 commit
    • Dave DeMarle's avatar
      fix a bug in value painting for cell arrays · 78108633
      Dave DeMarle authored
      I wasn't rendering the correct values because I didn't have the right
      ids. With small data the cellarray and polydata indices happened to
      be the same. In general they won't be.
      Change-Id: Id1186c8fab3b0ba0ff2e640a6fd3d6075f690516
  27. 29 Oct, 2014 3 commits
    • Ben Boeckel's avatar
      cmake: remove arguments to else and endfoo commands · fd26999f
      Ben Boeckel authored
      They're unnecessary and annoying to keep in-sync anyways. Just remove
      Change-Id: If7327e0cef17fa1c2d3d41877c4ff7568802fd41
    • Ken Martin's avatar
      Restore file that was accidentally changed · 4362136d
      Ken Martin authored
      Change-Id: I262b5e05433c1677c5c8fc5e14aaabc07ec0d68c
    • Ken Martin's avatar
      Get render passes working in OpenGL2 · f15f4bfe
      Ken Martin authored
      Add in a bunch of render pass classes that were previously removed.
      At the same time get the GaussianBlurPass and SobelGradientMagnitude
      classes to work with the new backend.
      This code now exercises a few methods that previously were not
      previously exercised. As such I made some significant changes to those
      methods to make them fit in better with the new architecture.
      In the process of testing I did find a calculation error in the old
      code related to cmoputing camera angles. I fixed this issue in both the
      old and new rendering backend.
      The tests for these passes were modified to not use the DepthPeelingPass
      as that pass has not been converted yet.
      Change-Id: Ie40231385291aa06848034460817b171e60f7a53