This has been implemented. Tools/ Customize Shortcuts.
https://gitlab.kitware.com/paraview/paraview/issues/17542. This slipped from 5.5.0 to next fall, 5.6.0.Alan supported this idea ·
So, to elaborate, you want an opacity set by one data variable, and the color by a different data variable? If you can use the same variable, ParaView will do this. Edit/ Color Editor/ Enable Opacity Mapping for Surfaces
VTK File Formats are now found online here: https://lorensen.github.io/VTKExamples/site/VTKFileFormats/
1) The goal is to get rid of junk like this. If you see warnings (or FIXME etc.), please create a bug.
2) The Output window can now be hidden (somewhat). Drag it to the Properties tab, and move it to be the tab under the Information tab.
I believe it is Sources -> Ruler.
Added to the todo list for fall.
I believe this now works, and actually has for a long time.
* Open can.exo.
* Right click Clip, Change Input, selecting disk_out_ref.
* There is a trivial bug that requires you to torn visibility off for the original disk_out_ref.exo.
This can be done with macros. Record a trace, save as macro.
This has somewhat been implemented. in the GUI, the X, Y and Z keys do work, allowing a user to rotate around the X, Y and Z axis.
Sorry for taking so long. https://gitlab.kitware.com/paraview/paraview/issues/16902. Depending on workload, scheduled for PV 5.3.
This will put the data and state file in the same directory.
Additionally, https://gitlab.kitware.com/paraview/paraview/issues/16900 will add optional relative paths to the state files.
We are going to add the ability to color contours by annotated colors (like we now do with blocks). this should occur in PV version 5.3. This does not replace contour labels, but supplements them. Labeling contours is under evaluation. https://gitlab.kitware.com/paraview/paraview/issues/15810