Cube Axes Labelling Untransformed ranges
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
PROBLEM: If mesh is transformed using Display tab (Z*10, etc) cube axes show only result of this transform, not original mesh coordinates in tics and labels.
SOLUTION: Add additional option toggle, letting user set application specific context of tic labels, either transformed or untransformed. Make default transformed, so will not be disruptive change.
PATCH: patched files: vtkCubeAxesRepresentation.[h,cxx], pqCubeAxesEditorDialog.cxx, pqCubeAxesEditorDialog.ui, views_and_representations.xml action: copy vtkCubeAxesRepresentation.[h,cxx] to ParaView-3.14.0/ParaViewCore/ClientServerCore copy pqCubeAxesEditorDialog.cxx to ParaView-3.14.0/Qt/Components copy pqCubeAxesEditorDialog.ui to ParaView-3.14.0/Qt/Components/Resources/UI copy views_and_representations.xml to ParaView-3.14.0/ParaViewCore/ServerImplementation/Resources
DESCRIPTION: When we load terrain mesh, scale it along Z axis (e.g. x5) and turn on cube axes around that pipeline item, axes labels for Z axis range will also be scaled (x5). In case we want to represent terrain's elevation by using cube axes, or generally to represent original data's extent with axes, this scaling will make cube axes inappropriate. To fix this behavior, our patch adds new property, UnscaledTicks, which controls if tick labels on axes are generated from original data or from transformed representation.
CHANGES: To make this patch, following changes were made (ParaView source patch):
- vtkCubeAxesRepresentation.[h,cxx] - Added UnscaledTicks property and Set[XYZ]AxisRange() / SetBounds() logic depending on flag's value,
- views_and_representations.xml - Added UnscaledTicks PQ property to vtkCubeAxesRepresentation class,
- pqCubeAxesEditorDialog.ui - Added UnscaledTicks check-box to Cube Axes Editor Dialog,
- pqCubeAxesEditorDialog.cxx - Added registering of PQ link between UnscaledTicks check box and representation property.