1. 28 Jun, 2012 2 commits
  2. 27 Jun, 2012 1 commit
  3. 19 Jun, 2012 1 commit
  4. 14 Jun, 2012 1 commit
  5. 13 Jun, 2012 1 commit
  6. 06 Jun, 2012 2 commits
  7. 04 Jun, 2012 1 commit
  8. 29 May, 2012 1 commit
  9. 28 May, 2012 7 commits
  10. 27 May, 2012 2 commits
    • Utkarsh Ayachit's avatar
      BUG #12542. Added support for interactive mode using outlines. · b23749cd
      Utkarsh Ayachit authored
      Removing ClientOutlineThreshold - it was used to control when to deliver
      outlines to client for interactive renders. Instead, added a checkbox to the
      "LOD Parameters" dialog to indicate that when using LOD, use outlines. When
      checked, if the view decides to use LOD rendering for interactive renders (based
      on the LOD threshold), it will use outline for the LOD instead of
    • Utkarsh Ayachit's avatar
      Fixed deadlock when opening Exodus file in parallel. · dcb5dc3d
      Utkarsh Ayachit authored
      Since vtkPVSILInformation is RootOnly information object, calling
      vtkAlgorithm::UpdateInformation() is scary since if the algorithm does
      indeed update the information, it will only happen on the root node and
      cause deadlocks (e.g. pvcs.GridConnectivity). Since information objects are
      only expected to gather information currently available, we shouldn't be
      calling UpdateInformation() in vtkPVSILInformation::CopyFromObject() in the
      first place. Fixed that by removing the UpdateInformation().
  11. 25 May, 2012 3 commits
    • Kyle Lutz's avatar
      Forward declare vtkMoleculeMapper in vtkMoleculeRepresentation · d2368917
      Kyle Lutz authored
      This fixes a failing header test by forward declaring vtkMoleculeMapper
      in the vtkMoleculeRepresentation header file.
      Change-Id: Iad579862a52696169d3b650ba7778c00e4bd3a31
    • Utkarsh Ayachit's avatar
      Fixed issue with comparative views. · 1124f5f3
      Utkarsh Ayachit authored
      After the latest round of refactors, the comparative views were broken. This
      happeneded since we removed the code that forwarded the cache related values to
      the internal representations in vtkCompositeRepresentation. That was a mistake.
      Consequently, when the cache keys were set on the representation's properties by
      the vtkPVComparativeView, they pretty much had no effect and the comparative
      view ended up rendering incorrectly. Fixed that.
      Change-Id: Ib89fdb06b1fd4438a2c19cd3a567b862051157a0
    • Utkarsh Ayachit's avatar
      Fixed Slice representation in client-server modes. · 41b198fe
      Utkarsh Ayachit authored
      vtkPVDataDeliveryManager was ending up not requesting new data when slice
      parameters were changed. This happened because the mtime we used in
      vtkPVDataDeliveryManager used the data-time, which clearly didn't change on the
      client after every update. Since vtkPVDataDeliveryManager::SetPiece() uses the
      executive's data-time to check if data was really updated, we shouldn't use the
      data mtime in vtkPVDataDeliveryManager's SetDataObject() call.
  12. 24 May, 2012 2 commits
  13. 22 May, 2012 1 commit
  14. 21 May, 2012 3 commits
  15. 20 May, 2012 2 commits
    • Utkarsh Ayachit's avatar
      Cleaned up ordered compositing code. · d2fe1dd8
      Utkarsh Ayachit authored
      * Reintroduced support for generating kdtree using image data extents.
      * Restructured code to ensure redistribution happens correctly for every render.
        The previous implementation required that the client triggered the
        redistribution in Delivery() call which was not possible esp. as
        representations were added/removed (since Delivery() is only called when data
        really needs to be delivered which is not the case when representations are
    • Utkarsh Ayachit's avatar
      Fixed bug with geometry not being delivered after threshold change. · 2fbfea69
      Utkarsh Ayachit authored
      This fixes the issue reproducible as follows:
      With remote render enabled create a sphere and hit apply. Now change the remote
      render threshold (from Python or GUI) to a large value (forcing local render).
      One would not see anything rendered, since the client was under the impression
      that the geometry had already been delivered. Fixed that by keeping separate
      timestamps on the client side to determine when geometry has been deliveryed in
      what rendering mode.
  16. 19 May, 2012 1 commit
    • Utkarsh Ayachit's avatar
      Refactoring surface-selection mechanism. · ef2cf1ae
      Utkarsh Ayachit authored
      * Surface selection now works in local-rendering mode (as well as remote
        rendering mode). It expects the vtkPVGeometryFilter to generate process ids
        (vtkProcessId) array in parallel. When present, it is used to determine the
        process id.
      * Selection rendering passes now render the "original ids" rather than the
        point/cell ids. Thus representations no longer need to "convert" selection.
        They just need to ensure that they render the correct ids in the selection
        rendering passes.
      This makes it possible to determine the "selection" directly on the client.
      Thus, we no longer need to gather the selection from the server side.
  17. 18 May, 2012 9 commits