@lassoan : Great insight about evaluating the impact using github directly. Very interesting approach. Also reading the issues you sentiment seems to be definitely shared between VTK users. One of note from a pyvista user (context):
We wouldn’t blame you for being ruthlessly annoyed by the continual deprecation churn from Vtk. We kinda are. Like, seriously. Vtk, can you just slow down that moving API target a little there? face_exhaling
Looks like there is an agreement about the usefullness of this API, so I will move forward with the restoration of the API.
That being said, this should have been caught much earlier imo in order to avoid forcing VTK users to change their use of VTK.
@lassoan , it looks like @jcfr and yourself fixed that in slicer in June, what made you open this thread now and not at the time ? I’m just trying to understand what I did wrong here (apart misdjuging the usefulness of an API).