We discussed while @jaswant.panchumarti was implementing this and decided it was not very important for ParaView to support this. Perhaps in a batch script you might want the camera setting? That feels like a not common use case to me.
I don't see any relevant changes to Wrapping/Python/paraview/coprocessing.py
in the last month.
"Ids" is consistent with filters that have "Ids" in their name, so my vote is for that.
+2
+2
I see, that makes sense.
What is reporting the memory usage? Operating systems are notoriously bad at reporting accurate memory usage in my experience.
Sorry, what's the question?
Wheels failed right away in your latest pipeline.
Looking good!
Does the "Consistency" property need to be defined before the "FeatureAngle" property for this decorator to work? If not, consider sticking with the previous order to minimize code changes.
Ah, I see. In such cases, consider marking this as a draft.
For VTK bumps, please use the git bump
command, installed by Utilities/SetUpForDevelopment.sh
(you can rerun it no problem if you have already run it). This adds a helpful commit messages about what the VTK bump is bringing in automaticall.
The additional info is not all that helpful, IMO. It doesn't say how to actually change the threshold using the cited tools.
Better would be to have a paragraph or two in https://gitlab.kitware.com/vtk/vtk/-/blob/master/Documentation/docs/developers_guide/git/test.md?ref_type=heads#add-test.
+2
Perfect, thanks!
Please include more info about why this change is being made in the commit message and description.
Otherwise, +2
+2
+2
Bummer, the "build" stage is totally not working with this change.