LabVIEW
Identify obscure LabVIEW method
Solved!
For me its Find All Instances, Select Type for polymorphic VIs (I have plenty), and Create Constant/Control/Indicator.
@altenbach wrote:
I use "SubVI Node Setup" quite often.
That's because there *is* an "oldest trick in the book."
Madest thou look.
@Darren wrote:
altenbach is right, this feature is still available in LabVIEW today. Here it is in LabVIEW 2013:
P.S. - Nobody actually uses this feature. 😛
I used it in the past a few times (LabVIEW 5.x or so) but learned quickly that it was kind of cumbersome. The datalog format changes with every LabVIEW version so that when you upgrade a VI you have to go through upgrading the data log file too in order to use it and my biggest gripes with this functionality was that there was no good interface to actually access the logged data. Yes replaying it in the user interface of the VI was an option save from reading the data in records, but the replay was rather limited in its efficiency when having to look through bigger data and the retrieval could only do sequential access, so that was rather cumbersome. Didn't really help when debugging a function and a simple message logger placed at strategic locations in a VI helped much more and would create a log file that was easily parsable by all kinds of post processing tools including command line grep :-).
@Hooovahh wrote:
For me its Find All Instances, Select Type for polymorphic VIs (I have plenty), and Create Constant/Control/Indicator.
I Use Find all Instances also quite regularly together with Properties sometimes. Have stopped setting up SubVI Node setup in here as it makes it rather hard to maintain how a VI appears and where and when it does what it does. Prefer explicit setting of anything UI related in the SubVI itself through Property Nodes, so that there are no hidden configuration settings that you can't see when looking at the diagram alone.
At a previous client, some bright C coding types had LabVIEW code with worst case con panes (Ouch) Very difficult to correctly wire! Right-Click, un-check View as Icon was pretty handy. When the rest of the developers saw my BD they asked "WHAT IS THAT?!
"
Me: "Oh, THAT is a VI. Haven't you ever seen a vi before?"
@ Raven's Fan: the search term was "Enable Database Access" WITH the quotes. The link is the top of five returned results. Of course I tried without quotes first and would never have seen that page so, I thought the link was a good idea.
Right-Click, un-check View as Icon was pretty handy.
There was a question posted in the past about the types of things to ask during an interview. One of the questions suggested was to ask how they prefer to see control terminals on the block diagram. As I icons or not. It wasn't suggested to not hire those who say to use the icon view, but simply that it was a data point to get to know the persons experience, and coding style.
Jeff·Þ·Bohrer wrote:
@ Raven's Fan: the search term was "Enable Database Access" WITH the quotes. The link is the top of five returned results. Of course I tried without quotes first and would never have seen that page so, I thought the link was a good idea.
Seems like this is a complaint about the search function, seeing as google comes up with the right answer.
This has been a fun conversation to watch.
I think though that some kudos are appropriate to the guy who started it... or maybe extra points for when I take the CLD in a few weeks...
Dan
