LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
Top Kudoed Authors
Showing results for 
Search instead for 
Did you mean: 

Add "in range" condition to Conditional Signed32 Probe

Currently the Conditional Signed32 Probe only offers the following conditions:

current conditions.PNG

 

I would like for the "In range" condition to be added (excuse the poor image):

 

proposed conditions.png

4 Comments
Knight of NI Knight of NI
Knight of NI

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.

Active Participant FabiolaDelaCueva Active Participant
Active Participant

I thought about it after posting it, you are right, we should probably have both options.  In range and Out of range.

Proven Zealot
Proven Zealot

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.

Trusted Enthusiast
Trusted Enthusiast

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.