Darren

To my knowledge, this VI does not ship with LabVIEW. I wrote it myself for this thread back in '08, and it's been sitting in my "VI_Utils" folder on my computer ever since. -D

The VI uses a private VI Server method that can read linkage information from the .lvclass file on disk. As a general rule, we (that is, LabVIEW R&D) password-protect any VIs that contain private functionality when we post them on public forums. -D

It looks like my attachment to this thread was lost during the LAVA site redesign. Here it is again (saved in LabVIEW 8.6). -D Get Class Hierarchy from Disk.vi

"if you try to idiot proof your UI, they will build a better idiot..." I foresee myself quoting this many times in the future... -D

I think you're looking for [LabVIEW]\resource\Framework\Providers\LVClassLibrary\CLSUIP_MemberTemplate.vit. I changed the structure in there to not Auto Grow, and my new static/dynamic dispatch VIs no longer had Auto Grow set. -D

It is my understanding that calling an XNode (either by a subVI call or otherwise) within another XNode is simply not supported. -D

And if you've already created a bunch of VIs with Auto Grow enabled, you can run this utility to turn it off on all structures in all VIs in a given folder. Turn Off Auto Grow -D

Should I post this as a weekly nugget? I assumed it was well-known, but if two LAVA guys didn't know about it, that probably translates to way more 'regular' LV programmers not knowing... -D

Show the Boolean Text of the checkbox instead of the Label. This will give you the behavior you're looking for. -D

Stylistically, I almost never close a passed-in reference in a subVI. I always close it in the same VI that opened/generated it. That way I don't have to worry about a reference that I think is valid actually being invalid because it was closed in a subVI somewhere beforehand. -D

The wikipedia article gives more info about number of takes, size of engineering team, etc. If you look carefully in the background during the TV smashing part, you can see all the smashed TVs from previous takes that didn't work out. Similarly, there's a smashed piano in the background during the piano drop...apparently they had to do that one at least twice.

I've been to a few brainstorming meetings that used some kind of Mind Map software. It seemed like a solution looking for a problem to me. I prefer good ol' whiteboards and notetaking. -D

The keyboard shortcut for the Revision History dialog box in LabVIEW is Ctrl-Y. Could there be some config option in the Windows speech settings that is making it try to convert whatever you're saying into a Ctrl-command? Just a thought, -D

I think I've seen this issue posted on the NI Forums a few times, and I think it has to do with having an Event Structure in your 2009 diagram and attempting to save to 8.5. I think there are some workarounds posted. -D

Be careful with that, as there are some problems when converting null data from a database with the regular Variant To Data function that the DB Variant To Data function handles correctly. Also, I think the Timestamp issue was fixed in the Database Toolkit at some point, but I don't remember which LabVIEW version it was. -D

I posted a response in the thread on the NI Forums...I think we should probably continue the conversation there since it has the entirety of the conversation. -D

Yeah, I used to play the games on here a lot, but there's so many alternatives at this point that it probably doesn't make sense to put any effort into bringing them back here...well, unless it's a gallery of LabVIEW-based games, that is... -D

The new LAVA doesn't have any games. I haven't heard Michael mention bringing them back, either. -D

The VI Analyzer Spell Check test harvests all the words from a VI...you could probably steal some of its code to find words and replace them. -D

From one CLAburger to another, congrats! -D

Even though you can't get official support from NI for the older versions, I'm running LabVIEW 7.0, 7.1, 8.0, 8.2, 8.5, 8.6 and 2009 on my Windows 7 64-bit machine and haven't seen any problems with any of them, installation or otherwise. -D

I filed CAR# 191973 on this issue. Unfortunately, I don't know of a workaround. -D

Rolf is right...there's no need to run a LabVIEW patch (like an 'f1') unless you are experiencing the exact issue described as fixed in the patch. The Service Packs, on the other hand, will contain several bug fixes and potential performance enhancements, and are intended for all users of that particular version.

I posted a utility VI that does this here. -D

As promised, here's my blog post on creating your own Quick Drop keyboard shortcuts in LabVIEW 2009. -D