LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
Miraz_Automation

Make ctrl+click swap the wires on the top and bottom terminals of "In Range and Coerce" function

Status: New

"In Range and Coerce" function should have swap terminal option. The upper and lower limit shall get swaped.

 

swap.png

With Regards

Miraz
Kudos is better option to thank somebody on this forum
------------------------------------------------------------------------------
15 Comments
Mads
Active Participant

Ravensfan - if you read my post one more time you will see that I talked about switcheroo-functionality, so no misunderstanding there. 

However, now that tst has explained the idea a bit more we know that it was not switcheroo-funtionality he is aiming for after all, so we are both wrongSmiley Wink

 

Rephrasing the node to just say that it is a "is the value between these two values", and not define any of the range parameters as either min or max - makes me kind of like the idea better. That way the order of the range inputs do not really matter.

 

PS. Living in Bergen I pretty much use the wipers more than I do not, and I do not swap cars that often so I get used to one of the two ways to operate them...and always get annoyed when I switch to a car with the oppsite logic. The point was mainly just to illustrate though that the world is filled with these little variations though, for no apparent reason (other than to annoy or keep us on our toes I guess Smiley Frustrated). The true version of your idea tst makes it less annoying though, because implicitly it removes the whole need/possibility of a subjectively chosen order.

RavensFan
Knight of NI

I don't think tst is able to explain the idea a bit more.  It is his intepretation of what he wants.  He is not the original poster.  And has said that he already has an idea open that is based on the other interpreation of what he wants (ie.  an IRC function that doesn't care about which is upper and which is lower.)

 

All I can go by is the original poster's actual words and he says "Yes I am expecting a switchroo functionality, I was not recollecting the name"

 

 

Miraz_Automation
Member

Hello All,


I just showed the idea with constant attached to upper and lower limits, because of this you might be thinking, having lower limit at top and upper limit at bottom after applying switchroo functionality may not be a good idea.

 

But if we are applying limits from some shift registers or if limit values are coming from subVI then switchroo will make it easy to switch limits.

With Regards

Miraz
Kudos is better option to thank somebody on this forum
------------------------------------------------------------------------------
Yamaeda
Proven Zealot

This idea could also be extended to the Select-function, it'd make code cleaning easier.

/Y

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
Yamaeda
Proven Zealot

That's what you get for being stuck in an old LV in the project. It's already implemented on Selects. 🙂

/Y

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer