Let’s take it as a given that these are not easy decisions and the ones putting in the work deserve our appreciation for keeping the code maintained. Let’s also try to learn from each decision and try to make things easier for all of us going forward. I empathize with @lassoan and I can easily imagine myself with some broken code someday that required tracing back to find the replacement for ThresholdBetween and wondering why it was removed. I’d like to see VTK avoid that situation as much as possible and keep the API change bar set pretty high, deprecation warnings or not.
1 Like