Sebastien Jourdain authored 8 years ago and Kitware Robot committed 8 years ago

aff468c4 Add dataset builder for vtk-js

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1407

T.J. Corona authored 8 years ago and Kitware Robot committed 8 years ago

130b83a2 Update VTK to latest master.

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1404

Joachim Pouderoux authored 8 years ago and Kitware Robot committed 8 years ago

f4d77a93 Allow vtkMPIMoveData to process StructuredGridData.

Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Mathieu Westphal <mathieu.westphal@kitware.com>
Acked-by: Bastien Jacquet <bastien.jacquet@kitware.com>
Merge-request: !1397

David E DeMarle authored 8 years ago and Kitware Robot committed 8 years ago

90612793 adjust to new value render check signature
49b24286 bump VTK to access float textures support on more platforms

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1402

Utkarsh Ayachit authored 8 years ago and Kitware Robot committed 8 years ago

c67dc704 Remove obsolete pq3DWidgetFactory/pq3DWidgetImplementation.
b2c31c15 Fix version number.

Acked-by: Kitware Robot <kwrobot@kitware.com>
Reviewed-by: Cory Quammen <cory.quammen@kitware.com>
Reviewed-by: Shawn Waldon <shawn.waldon@kitware.com>
Merge-request: !1401

Cory Quammen authored 8 years ago and Kitware Robot committed 8 years ago

d96f78fd Modify vtkPVGeometryFilter to handle quadratic ghost cells

Acked-by: Kitware Robot <kwrobot@kitware.com>
Reviewed-by: Utkarsh Ayachit <utkarsh.ayachit@kitware.com>
Merge-request: !1391

The vtkPVGeometryFilter delegates surface extraction in the case of
unstructured grids to vtkUnstructuredGridGeometryFilter. However, the
vtkUnstructuredGridGeometryFilter was clipping ghost cells, resulting
in extraneous boundary cells being added to the extracted surface.

This change disables clipping of ghost cells in the delegate filter,
leading to correct surface geometry generation.

Added test with quadratic ghost cell data.

Andrew Bauer authored 8 years ago and Kitware Robot committed 8 years ago

ad31113f Getting rid of CMake warnings in Catalyst adaptors

Acked-by: Kitware Robot <kwrobot@kitware.com>
Reviewed-by: Ben Boeckel <ben.boeckel@kitware.com>
Merge-request: !1398

Utkarsh Ayachit authored 8 years ago and Kitware Robot committed 8 years ago

f5fe121f Update VTK to pull in the text rendering fix for #17156

Acked-by: Kitware Robot <kwrobot@kitware.com>
Reviewed-by: Cory Quammen <cory.quammen@kitware.com>
Merge-request: !1392

Utkarsh Ayachit authored 8 years ago and Kitware Robot committed 8 years ago

7b853c03 Fix issues with Qt 5 static plugins.

Acked-by: Kitware Robot <kwrobot@kitware.com>
Reviewed-by: Ben Boeckel <ben.boeckel@kitware.com>
Merge-request: !1389

Also removing ARGS since it is ignored now and not necessary

Utkarsh Ayachit authored 8 years ago and Kitware Robot committed 8 years ago

61251146 doc: add some docs to vtkSMParaViewPipelineController.
c6735eae Remove obolete code to handle LZ4 support.
c1954d50 Fix tracing/saving state of representation property.

Acked-by: Kitware Robot <kwrobot@kitware.com>
Reviewed-by: Andrew Bauer <andy.bauer@kitware.com>
Merge-request: !1396

This feature is needed for some representations that would process
structured grids directly.

Code was not needed since 5.1. Removed it.

Addresses #17196.

The issue is a tricky one. Here's the synopsis. When tracing or saving
state in Python, we only save state for properties that are different
from the default. This generally is a good strategy for minimizing trace
verbosity. Now, for a property with `vtkSMRepresentationTypeDomain`, the
default is changed by the domain (in our case to `Outline` from
`Surface`). For the bug, we changed it back to `Surface` -- now same as
default. Hence, when saving the state file, the code skipped the
property as it's value was unchanged from the default -- causing the
bug.

As a fix, we force the tracing mechanism (also used in when saving state
as Python) to save the "Representation" property, even if it hasn't
changed from the default value.

A better fix maybe to add support to vtkSMProperty to know that it was
changed since initialization -- but that needs some pondering.

Utkarsh Ayachit authored 8 years ago and Kitware Robot committed 8 years ago

5a4fedd4 Trace scalar bar movements.

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1394

Addresses #17113. Scalar bar interactions are now traced in Python.

Utkarsh Ayachit authored 8 years ago and Kitware Robot committed 8 years ago

7ead515b Addresses Issue #17198.
de2bc586 Fix scalar bar placement in Python state.

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1393

`Orientation` needs be changed before changing the position properties
on the Scalar bar. Ensuring that we do that.

The `Orientation` property needs to be set before the `Position*`
properties on the scalar bar for it to work correctly. While this
requirement is absurd, it's the legacy scalar bar! Hence just fixing the
Python state to save out the order correctly. This is done by simply
reordering the properties in XML since the Python state preserves XML
order for properties.

Addresses #17197.

Utkarsh Ayachit authored 8 years ago and Kitware Robot committed 8 years ago

a52d1b98 Update test XML after UI changes to address #17144.
65ea07bb Updating comment as requested.
b135061b Add prompts for user to lock ranges after rescale.
b8b5cc71 Add rescale-n-lock prompt to pqRescaleRange.
27fd6b9a Remove old "LookupTable" proxy.
3d4ec941 Consolidate reset scalar range code to pqResetScalarRangeReaction.
1e1a099a Consolidate code to reset color map range to custom.

Acked-by: Kitware Robot <kwrobot@kitware.com>
Reviewed-by: Cory Quammen <cory.quammen@kitware.com>
Merge-request: !1386

As requested in #17144, this does the following:
1. allow user to rescale and lock, or simply rescale when rescale range
   to data over time or custom range.
2. unlock range when "rescale to data" is clicked.

pqRescaleRange now lets user choose whether to lock the range as it
rescales the color map range.

The Qt macro usage was incorrect. Addresses #17157.

Utkarsh Ayachit authored 8 years ago and Kitware Robot committed 8 years ago

78390a72 Check for empty views (addresses #17186).

Acked-by: Kitware Robot <kwrobot@kitware.com>
Reviewed-by: Cory Quammen <cory.quammen@kitware.com>
Reviewed-by: Shawn Waldon <shawn.waldon@kitware.com>
Merge-request: !1388

Ken Martin authored 8 years ago and Kitware Robot committed 8 years ago

a7a434df expose key texturemap toplane settings

Acked-by: Kitware Robot <kwrobot@kitware.com>
Reviewed-by: Utkarsh Ayachit <utkarsh.ayachit@kitware.com>
Merge-request: !1373

We have not used it since old ParaView 2.0 days.

Consolidated all code to rescaling color map ranges in various ways to
pqResetScalarRangeReaction and removed
pqRescaleCustomScalarRangeReaction and
pqRescaleVisibleScalarRangeReaction.

pqColorOpacityEditorWidget now uses pqResetScalarRangeReaction to reset
color map range to a custom range.