GitLab

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.

Fixes #18928. The issue was arising due to a bug in vtkSMViewLayoutProxy
where it did not consider separator width when positioning views in the
layout. Fixed that.

Improve support for stereo screenshots. vtkSMViewProxy now explicitly
handles the stereo left-right compositing after rendering each eye
separately. This is required to support stereo captures that need
tiling. Fixes #18974.

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

vtkSMViewLayoutProxy was not pushing its custom state to the server side
when XML state was loaded. Fixed that.

fixes #19006.

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.

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.

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.

This change adds the Export Now button to the Catalyst menu (only if
PYTHON is enabled like the other contents). When pressed, ParaView will
animate through the available timesteps and export the same set of data
products (writers and screenshots) that Catalyst is configured to do.

As with catalyst, we now cinema export repeatedly, once per timestep,
wheras for the original file export path we would call once and have
cinema do the loop

We instantiate serial writers in when we don't have access to the
parallel counterparts.

To expand for Cinema D, the cinema image library changed to keep a
record of every new file it writes, along with the parameters that
produced it. cinema D export gets that information and dynamically
creates an expanded set of keys to save out at the end

hide object track and roll parameters without composite. It was
broken in 5.6.0.RC3 when spaces were removed from the property names.

catalyst export expands cinema A-C into D too

add a reasonably complete regression test that ensures that the
code paths run and that the newish index file and subdirectory at least
exist after the run.

This reverts commit 354c09da.

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.

Adding support for logging using vtkLogger in ParaView.

* command line options (-v) enable users to specify log verbosity for
  messages shown on stderr by default.
* command line options (-l) allow users to request multiple log files with
  different verbosities.
* vtkPVLogger implements a category-based logging framework that allows
  users to elevate log levels for predefined categories at runtime using
  environment variables.
* proxies support a logname attribute that gets set with user
  friendly name to make it easier to interpret log messages.

Updating lut APIS in simple to use the newer mechanisms and thus fixing
issue #17616.

BagPlot vilters and related views taget a specific usecase
and can't be used by most users. All ParaView side classes and files
have been moved to a new plugins and PipelineIcon hints have been
used so a specific icon is shown for the ExtractBagPlot filter

This enables xml filter dev to specify the pipeline icon to use with a specific filter
It can be either a view type name or an existing icon ressource or nullptr.

@code{xml}
 <SourceProxy>
   <Hints>
     <PipelineIcon name="<view name or icon ressource>" port="<output port number>" />
   </Hints>
 </SourceProxy>
@endcode

ParaView was checking that inherited properties were the same name and
type, but not that they had the same number of elements. This resulted
in an error message when a TextRepresentation would inherit from a
UnstructuredGridRepresentation, for example. Both representations have
an Orientation property, but they have a different number of elements.

expose some mapper parameters:
 - atoms/bonds visiblity,
 - radius values/scale/type

presets are also available from proxy

The MoveSubtree() function moves trees from lower down in the KDTree
up. The existing depth-first traversal recursive algorithm in this
function worked okay when descending the tree, but when moving back up
the tree, elements in the array would be clobbered before they were
moved to their correct destination. This would lead to some views
being incorrectly deleted and moved into the wrong location when a
level of the KDTree was being collapsed.

Change to a breadth-first algorithm so that elements in the tree are
always copied from lower to higher positions in the tree. This
resolves the incorrect subtree movement.

Better default configuration now managed by the domain
Multiple corrections to the widget/dialog duality
Added a "Reset to domain" button
Updated tests
Fix #18561

A new ColorSpace has been added in VTK, this uses it.
This add a few Step Color Map preset
This adds also .md and test

This is a temporary fix for #18446. To make vtkSMViewProxy use offscreen
buffers for screen capture, we now support an environment variable
`PV_USE_OFFSCREEN_BUFFERS_FOR_IMAGE_CAPTURE`.

two new pieces of global state:
 time compartment size, the number of ranks to use per timestep
 input filepattern for readers that begin the pipeline

input filepattern used to be per source, and was specified via
the channel matching section of the dialog. Per discussion with Andy
multiple readers are not really well supported anyway so simplify
to a global filepattern.

fixed some bugs in the original plugin that this deprecates, involving
a lookup into map of views that failed with no name, and code rot
where the base paraview python API changed and made it incompatible

vtkSMDataDeliveryManager needs to keep track of lod/non-lod delivery
timestamps separately as the same delivery mode may be used for both.
Fixes #18419.

Fixes #18304.

When doing remote rendering, the client's mtime for when data delivery
happened was not correctly updated. That was causing the data delivery
logic to reexecute on each render. That was causing #18340.

Fixed vtkPVDataDeliveryManager to keep separate delivery objects for
each delivery mode. This ensures that the client doesn't end up with a
data delivery timestamp mismatch, as before. Also simplified the code in
general and adding timer log entries to catch such bug easily in the
future.

Fixes #18340.

`vtkPVRenderView::GetUseDistributedRenderingForStillRender` and
`vtkPVRenderView::GetUseDistributedRenderingForInteractiveRender` are
renamed to better reflect the implementation. These are not for still vs
interactive but full-res vs lod. New names avoid that confusion.

This commit was motivated by a fix for BUG #17739. This includes the
following improvements:

1. added properties on SpreadSheetView to control aspects like hidden
   columns. There were two mechanisms at play to control the columns
   that are hidden one in the Qt part and another in the View for
   exporting. Combined those to use a single approach.
2. Simplified pqSpreadSheetViewDecorator to update properties on the
   view for things like cell connectivity, field association etc. This
   make undo/redo, state save/restore work better for several of the
   parameters. A few still remain (see #18388).
3. Changed CSV export to use column labels. Also made CSV export always
   only export visible columns. The toggle we previosly exposed doesn't
   make sense. Export capability is meant to export what is shown in the
   view. The option to export extra columns was unnecessary.
4. Added a mechansim to vtkSMViewProxy subclasses to update their
   properties when representation are hidden/shown via the controller.
   vtkSMSpreadSheetViewProxy uses this mechanism to pick a good field
   association for the visible source.
5. pqExportReaction was messing up undo/redo stack. Fixed that.
   pqExportReaction should not be affecting the undo/redo stack at all.

(cherry picked from commit 4679f456)