Currently the Conditional Signed32 Probe only offers the following conditions:
I would like for the "In range" condition to be added (excuse the poor image):
If you add that, you might want to add "out of range" also. Actually, I think I'd be more likely to want to pause on something being out or range rather than in range.
I thought about it after posting it, you are right, we should probably have both options. In range and Out of range.
What about inclusive or exclusive of the endpoints as on the In Range and Coerce node?
It never ends. The list of things we could add to that comparision list is totally open. This is why we created custom probes -- so you could write whatever comparison you need.
I am not going to create a new idea for this, because from a development point of view, the nature of the suggestion and solution is similar, so here it is:
1. Add "Is Different From" (*)
2. Extend this to other numeric types
Combine 1 and 2 and you have "is a valid number" (Type: DBL and "Is Different from" NaN)?
I don't buy that this belongs to custom probes. This is the bread and butter of debugging nasty corner cases in numeric code.
(*) Or, in the spirit of Fabric's suggestion, add an option to "negate" a condition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.