1. 16 May, 2019 4 commits
    • Utkarsh Ayachit's avatar
      update boxwidget on use-reference-bound changes · 9a09f149
      Utkarsh Ayachit authored
      Fixes #19033. The box widget needed to faithfully follow the state of
      UseReferenceBounds even when the ReferenceBounds were overridden. By
      keeping PlaceWidget bounds and ReferenceBounds separate, we can support
      this use-case.
      Also added a test for this use-case.
    • Utkarsh Ayachit's avatar
      Box widget: improve box specification · 54cd7a79
      Utkarsh Ayachit authored
      Box implicit function was specified using a transform relative the data
      bounds which were not exposed in the UI. This made it extremely tricky
      to specify the box using absolute position/orientation/scale parameters.
      Fixed that.
      By default, now the box is always placed using absolute values i.e.
      relative to a unit box anchored at origin. Added a mode that enables
      user to provide an explicit bounding box to use for reference instead.
      This will make it possible to support legacy state files.
    • Utkarsh Ayachit's avatar
      vtkSMBoundsDomain: add component_magnitude mode · 683ef288
      Utkarsh Ayachit authored
      Adding a new mode to vtkSMBoundsDomain where each the range is magnitude
      for the bounds in each direction separately.
    • Utkarsh Ayachit's avatar
  2. 15 May, 2019 2 commits
  3. 14 May, 2019 2 commits
  4. 13 May, 2019 3 commits
  5. 10 May, 2019 1 commit
    • Mathieu Westphal's avatar
      Remove usage of GetDomain(name) · 9fb6d76f
      Mathieu Westphal authored
      This remove usages of GetDomain(name) and replaces them by FindDomain<class>()
      or FindDomain("class") in python.
      This also transform usages of FindDomain("class") into FindDomain<class>()
      This also add support for StringListDomain in python
  6. 09 May, 2019 4 commits
  7. 08 May, 2019 5 commits
  8. 06 May, 2019 2 commits
  9. 04 May, 2019 16 commits
    • Utkarsh Ayachit's avatar
      update python tests to assign views to layout · b477c50d
      Utkarsh Ayachit authored
      Since we no longer automatically create layouts when a view is created,
      we need to explicitly call `AssignViewToLayout` to assign a view to a
    • Utkarsh Ayachit's avatar
      Improve layout support in Python. · bcd98a1d
      Utkarsh Ayachit authored
      To fix #18964, pqMultiViewWidget no longer
      automatically grabs a newly created view. Instead association of a view
      with a layout is now an explicit action. This makes it possible to
      faithfully reproduce Python traces when played back in the Qt GUI.
      Since all views are now created 'detached', the APIs to create detached
      views is being removed since it's no longer applicable.
      Python state support was also imporved to correctly record view layouts.
      Previously, layouts were simply not saved in Python state files.
      SplitViewTrace and TraceMultiViews tests now do baseline compares to
      validate the fixes.
      Fixes #18964.
    • Utkarsh Ayachit's avatar
      fixes for comparative view. · c8bd3e70
      Utkarsh Ayachit authored
      For now, we don't support comparative views on tile displays and cave
      displays. We will add support for that later. These changes ensure that
      comparative views otherwise work as expected.
      Reported as #18985.
    • Utkarsh Ayachit's avatar
      update SaveScreenshot · 429bc0c8
      Utkarsh Ayachit authored
      the test can now compare plots too. updated acordingly.
    • Utkarsh Ayachit's avatar
      update baselines due to DPI changes. · 9ad34177
      Utkarsh Ayachit authored
      Previously in batch mode, the `vtkPVView::SetPPI` failed to propagate
      the DPI correctly to the underlying render window thus ending up using
      the default DPI instead. Since now the correct PPI is passed through,
      the baselines needed to be updated.
    • Utkarsh Ayachit's avatar
      avoid communicating with data-server when rendering · 9f41d59b
      Utkarsh Ayachit authored
      The data server is never involved in actual rendering. Let's not set
      rendering messages to it. The `asserts` added to
      `vtkPVRenderView::Render` helped catch this unnecessary communication in
      client-dataserver-renderserver mode.
    • Utkarsh Ayachit's avatar
      add test for cave display. · b9dc9cbf
      Utkarsh Ayachit authored
    • Utkarsh Ayachit's avatar
      vtkViewLayout: fixes for CAVE · 2961cbc3
      Utkarsh Ayachit authored
      vtkViewLayout support rendering a single view in CAVE mode. The active
      view is rendered on the cave display. This commit adds logic to ensure
      the windows are sized properly.
    • Utkarsh Ayachit's avatar
      fix tile display with translucent geometry · 93d49a24
      Utkarsh Ayachit authored
      Since vtkIceTCompositePass renders to full window irrespective of
      renderer's viewport, need to make sure that the vtkRenderer's viewport
      is updated to full size as well, otherwise internal passes like depth
      peeling can have issues when rendering on tile displays.
      Fixes #18978
      Updating TileDisplaySplitView to test translucent geomtry. Also added
      support to render larger tiles for better test image comparison.
    • Utkarsh Ayachit's avatar
    • Utkarsh Ayachit's avatar
      vtkIceTCompositePass: remove unnecessary stereo code · c43049db
      Utkarsh Ayachit authored
      vtkIceTCompositePass unnecessarily maintained separate color buffers for
      each eye. Since vtkRenderPass is full executed for each eye, there's
      nothing we need to do really. Even in client-server, each eye will be
      individually synchronized by vtkSynchronizedRenderer (or subclass).
    • Utkarsh Ayachit's avatar
    • Utkarsh Ayachit's avatar
      add support for active stereo · 85af0fba
      Utkarsh Ayachit authored
    • Utkarsh Ayachit's avatar
      fix delivery logic · cf0ea95a
      Utkarsh Ayachit authored
    • Utkarsh Ayachit's avatar
      refactoring remote rendering · ced8cf80
      Utkarsh Ayachit authored
      This commit cleans up the code that manages remote rendering.
      This fixes several issues: #15205, #17611, #18940, #18152, #18938,
      and #18937. #17815 is also addressed since its no longer applicable.
      ParaView no longer creates a single render window to use among all
      vtkPVView instances on non-client processes like pvbatch or pvserver,
      pvrenderserver. This shared render window was the root cause of several
      headaches and necessitated classes like vtkPVSynchronizedRenderWindows
      and extra burden on views to re-direct several calls like creating
      windows, resizing windows to vtkPVSynchronizedRenderWindows. This is no
      longer the case. Non-client processes still have a single viewable
      window per proceses (vtkPVProcessWindow). However, this is not the
      window that each view renders into. Instead, each view creates its own
      vtkRenderWindow subclass. However, it's a FBO-based render window which
      shares the context with the process specific render window
      (created in vtkPVProcessWindow). This makes it possible to simply blit
      back the rendering results from each view to the user-viewable window
      when needed (e.g. tile display, cave, etc.).
      `vtkPVSynchronizedRenderWindows` is now obsolete and removed with
      appropriate convenience API now moved over to vtkPVView. This also
      removes the need to initialize each view with a unique ID and hence
      `vtkPVView::Initialze()` API is no longer needed and hence removed.
      vtkIceTCompositePass was fixed to address several issues including tile
      display aspect ratios (#18152, #17611). vtkPVIceTCompositePass is no
      longer needed and hence removed which further simplifies the code.
    • Utkarsh Ayachit's avatar
      vtkPVHardwareSelector: cleanup debugging logic · 14766c7a
      Utkarsh Ayachit authored
      Cleaning up the logic to generate images for debugging to be more
  10. 03 May, 2019 1 commit