1. 23 Feb, 2021 2 commits
  2. 15 Dec, 2020 1 commit
  3. 28 Apr, 2020 1 commit
  4. 17 Apr, 2020 1 commit
  5. 09 Sep, 2019 1 commit
  6. 31 Mar, 2019 1 commit
    • Cory Quammen's avatar
      Use assert() in place of Q_ASSERT() · 51907f19
      Cory Quammen authored
      Q_ASSERT can lead to a spurious warning from MSVC (C4127: conditional
      expression is constant). assert() provides just as much information to
      developers as Q_ASSERT(), so use it instead.
  7. 14 Mar, 2019 1 commit
    • Utkarsh Ayachit's avatar
      updates to handle Qt/VTK OpenGL api changes. · 6956268f
      Utkarsh Ayachit authored
      1. handle API changes in QVTKOpenGLWidget, QVTKOpenGLNativeWidget.
      2. on macOS use QVTKOpenGLNativeWidget, on Windows and linux we
         QVTKOpenGLWidget. This makes it possible to support active stereo
         (quad buffer based stereo) on linux/windows.
  8. 31 Aug, 2017 1 commit
  9. 22 Feb, 2017 1 commit
  10. 15 Jan, 2017 1 commit
  11. 28 Dec, 2016 1 commit
    • Utkarsh Ayachit's avatar
      Cleanup undo/stack after interaction in chart views. · 550ecc48
      Utkarsh Ayachit authored
      When on interacted with any of the chart views, it messed up the
      undo/redo stack adding individual undo actions for each mouse move.
      Fixed that by ensuring that the entire interaction gets clubbed in a
      single undo event.
      Needed to add new vtkPVContextInteractorStyle class since
      vtkContextInteractorStyle does not fire start/end interaction events
      which are needed to build undo stack properly.
  12. 18 Oct, 2016 1 commit
  13. 20 Sep, 2016 1 commit
  14. 04 Apr, 2016 1 commit
  15. 31 Jan, 2015 2 commits
    • Utkarsh Ayachit's avatar
      Refactoring ParaView interaction code. · a5111d41
      Utkarsh Ayachit authored
      ParaView was subclassing vtkRenderWindowInteractor to create
      vtkPVGenericRenderWindowInteractor to handle interaction. That piece of code
      was potentially derrived from an older implementation of
      vtkRenderWindowInteractor and hence did what it did. Current implementation
      of vtkRenderWindowInteractor lets the vtkInteractionStyle (and subclasses)
      do all the heavy lifting. ParaView did that to some extent (since it has a
      vtkPVInteractorStyle), but will was relying on
      vtkPVGenericRenderWindowInteractor, vtkPVRenderViewProxy to propage
      interaction/still renders and other things. This has been refactored.  ParaView no
      longer uses a special vtkRenderWindowInteractor. All logic is handled by observers
      on the standard vtkRenderWindowInteractor.
      This change was done to make it easier to enable interactivity in pvpython.
      Added new API to simple.py to start interact with a view in pvpython.
      Change-Id: I9725be948174b12c7f306c1d2fdbcfaac2d352ee
    • Utkarsh Ayachit's avatar
      Refactor how pqView (and subclasses) create a QWidget. · 1c19e735
      Utkarsh Ayachit authored
      Change-Id: I10ab39ae104b61fbf2ba5cb5bd21b917ae70fc21
  16. 19 Sep, 2014 1 commit
  17. 17 Aug, 2014 1 commit
    • Joachim Pouderoux's avatar
      Introduce new classes for the new linked view Histogram representation. · 74df7fc6
      Joachim Pouderoux authored and Utkarsh Ayachit's avatar Utkarsh Ayachit committed
      This new view and the according representation allow to directly
      plot the histogram of an input dataset without manually applying
      the histogram filter on it. The representation manage the histogram
      table creation and also manage selection: the user can select one
      or more bars in the chart and it automatically selects the
      elements in the other views (3D, spreadsheet, etc.) that falls
      in the corresponding bins of the histogram. Note that the
      reverse operation is not supported: selecting elements in another
      view will not select corresponding histogram bars.
      As the parallel coordinates, the histogram view supports only one
      representation. It automatically switches representations to have
      only one visible.
      Change-Id: I481c9f8b27e8475175b503748db6686a143bc962
  18. 06 May, 2014 2 commits
    • Utkarsh Ayachit's avatar
      Cleaning up pqDisplayPolicy. · caae8297
      Utkarsh Ayachit authored
      Deprecating pqDisplayPolicy for the most part.
      vtkSMParaViewPipelineControllerWithRendering is now the class that
      manages all the logic in pqDisplayPolicy instead.
      Updating vtkSMViewProxy API to add CanDisplayData() which is needed for
      vtkSMParaViewPipelineControllerWithRendering to work correctly.
      Fixed usage of pqDisplayPolicy is core ParaView. Plugins and examples
      still need to be updated.
      Change-Id: I4188acaceedde2e0fe8e927e142b9a62615515f9
    • Utkarsh Ayachit's avatar
      Cleanup pqView::captureImage() API. · 6c989723
      Utkarsh Ayachit authored
      pqView subclasses don't really need to override captureImage(). Fixed
      that. For now, I am leaving pqComparativeRenderView unchanged. We need
      to move logic to capture image from pqComparativeRenderView to
      Change-Id: I87daec79b0da7f20ec87af96e4797675c873814f
  19. 12 Dec, 2013 1 commit
    • Cory Quammen's avatar
      Added Python view that enables plotting data with matplotlib · 797ae3a1
      Cory Quammen authored
      This view is compiled only if Python is enabled.
      The Python view accepts a Python script that can be used to plot
      data in a matplotlib figure. The script must contain two functions
      described below:
      - setup_data(view)
        The setup_data function supplies the current Python view as an
        argument. This is the native VTK object on which all methods that
        have been wrapped in Python may be called. The Python view supplies
        some methods that can be used to select which data arrays to
        transfer from the server side to the client side (all rendering is
        performed on the client). No arrays are selected by default.
      - render(view, figure):
        The render function supplies the current Python view as the first
        argument and a matplotlib FigureCanvasAgg as the second argument.
        The render function is typically expected to create one or more
        subplots in the figure that will be used for rendering.
      The functions setup_data and render may be defined in the script
      (e.g., when defined through the GUI settings for the Python View) or
      in the global Python interpreter (e.g. when defined in a script run by
      pvpython). They are invoked when needed by the Python view when
      rendering is needed.
      Removed unused saveImage() method from various views.
      Updated VTK to origin/master
      Change-Id: I882fa8eeacc81e8120762bf1312f568523559b09
  20. 31 Oct, 2013 1 commit
    • Utkarsh Ayachit's avatar
      BUG #14226: Fix selection on charts + find data · f8113ee4
      Utkarsh Ayachit authored
      Making pqContextView use the vtkSMSelectionHelper to create new selection proxy
      instead of the custom code. The custom code was not working correctly when the
      current selection source was not of the expected type. vtkSMSelectionHelper
      handles all those cases.
      Also removing obsolete code pqSelectionManager for creating selection sources.
      Use vtkSMSelectionHelper instead.
      Change-Id: Ia994af7cf04f2f9f97b202b10b6a617b96f2af83
  21. 30 May, 2013 1 commit
  22. 11 Oct, 2012 1 commit
  23. 15 May, 2012 1 commit
    • Yumin Yuan's avatar
      Modified some default mouse button actions for chart selection · dbebe87e
      Yumin Yuan authored
      By default in chart selection, the right-mouse-button will do selection
      for rectangle or polygon selection in charts. However when one of the
      Subtraction, Addition, Toggle selection mode is used, the
      left-mouse-button will be used for selection instead. Also, one of the
      right-button selection actions will always be active in charts.
      Change-Id: I4e64d4c2c122ce25efe58c9c560cd214c3436d65
  24. 14 May, 2012 1 commit
  25. 15 Mar, 2012 1 commit
  26. 13 Mar, 2012 1 commit
    • Utkarsh Ayachit's avatar
      Refactoring axis range properties for charts. · 5ed29efe
      Utkarsh Ayachit authored
      Charts did not save the updated axes ranges when the user interacted with the
      charts in the state files. This was because the property for axes range was
      not updated on interaction. Changing the entire infrastructure to get this
      Hence forth, as soon as the user interacts with the charts, the axes become
      "fixed" and don't auto-update unless user hits "reset-camera".
      There are 4 new properies LeftAxisRange, RightAxisRange, TopAxisRange, and
      BottomAxisRange that can be set to empty to enabled "auto" ranges or set to
      specific values to use those ranges.
      As soon as user interacts with the view, vtkSMContextViewProxy listens to the
      interaction event and updates the axes range properties using the current range,
      thus "fixing" them to the chosen values.
      Also creating special vtkContextViewInteractorStyle subclass to ensure that we
      call StillRender() on proxy every time the user interacts with the view.
      All these fixes now ensure that charts on tile displays show current axes ranges
      and update as user interacts with the charts.
      WIP: This breaks the synchronization of chart viewports in collaboration mode.
      That needs to be fixed.
  27. 23 Feb, 2012 1 commit
  28. 16 Feb, 2012 1 commit
    • Utkarsh Ayachit's avatar
      BUG #12932 and BUG #12930. Fixes size issues with plots. · 4a8c4116
      Utkarsh Ayachit authored
      The bug was that the size and position properties for plots were getting reset
      to default during initialization after the pqQVTKWidget had already updated them
      to correct values during resize() event handling (when the widget gets placed
      into the layout).
  29. 20 Jan, 2012 1 commit
    • Yumin Yuan's avatar
      ENH: Added new selection tool buttons to chart views. · c6d5654f
      Yumin Yuan authored
      New selection toolbuttons are added to the chart view frames for new
      selection mode in vtk charts. Currently the bar chart view is not
      supporting these new selection mode, so these buttons will not show
      in the bar chart view.
      Change-Id: I03a872d69b40b0c3bfe9b218f6e6e63ec12ea8d3
  30. 18 Nov, 2011 2 commits
  31. 24 Oct, 2011 1 commit
  32. 06 Oct, 2011 1 commit
  33. 28 Sep, 2011 1 commit
  34. 22 Aug, 2011 1 commit
  35. 11 Aug, 2011 1 commit
  36. 11 Apr, 2011 1 commit