Identify obscure LabVIEW method

[m3rl3n]

Altenbach is the MAN!!!

Amazing.

To continue the discussion of "you learn something new every day" and LabVIEW "attributes" that nobody uses....

I have been programming seriously in LV for almost 20 years and this is the first that I have ever come across this.  I did pull in the sub-vi and did the the right clicking thingy, and there it was.  Now I have to figure out why and how the original programmer was using this.

I'm sorry that I can't share any of the original code as this is still a classified project.  The customer wants it updated so it can be hosted on a Win 7 machine (with a different data stream interface device) and so it can support the program for another 10 to 15 years. So, I am bringing it from LV 3.x (converter used), currently at 7.1 and will continue with stops along the way at 8.6, 2009, 2011 & 2013.

Thanks for the help everyone!!

Dan

[billko]

Good luck. I suspect that LV will be the least of your worries...

[Ben]

"

P.S. - Nobody actually uses this feature.

"

My boss (CLA #5) uses that all of the time.

When VI Logging is enabled it will record every change to the GUI to a datalog file. It lets your record all of the user control changes along withthe data displayed.

It is handy to spot what the user ws doing when something went wrong.

Ben

[Michael_78]

I want the feature back!

[JÞB]

---

@Michael_78 wrote:
I want the feature back!

---

<Poof> Feature magically returns to all LabVIEW versions! (You are welcome Michael) 

Go read the thread again 

[crossrulz]

---

@Michael_78 wrote:
I want the feature back!

---

It's kind of hard to bring something back when it never went away...

[Michael_78]

Oops,  yesterday I narrowly missed the rube thread. Today its the stupid thread.  Still at least it was pointed out to me, a couple of times...

[RavensFan]

I have never seen this before either.

Jeff, how did you even manage to find this in the help file?  When I searched the help for Enable Database Access, I never found the page you linked to.  Most of the items I found were related to the DSC module.

[Hooovahh]

One of the most obscure features hidden under our noses.  I right click a subVI all the time but never used this or even thought about what it does.  As an exercise I couldn't help but right click on everything and see if I'm missing anything else.  Sure enough the Call Setup can be used very nicely to simplify my progress bar loading spash screen code I use.

I'm definitely going to use this to stump some LabVIEW masters.  Previously I used a lesser known feature that you can replace the front panel panes with tiled images.

EDIT: Never mind the Call Setup isn't as neat as I thought but I still didn't know it was there.

[RavensFan]

For me, I rarely have a reason to do a right click on an actual subVI.  Right clicking on a regular function, constant, or terminals are much more likely in order to get the properties dialog or set some other property that is a part of the right click menu.